Triple
T691719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Test of English as a Foreign Language |
E13805
|
entity |
| Predicate | registrationMethod |
P10740
|
FINISHED |
| Object | online registration |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: online registration | Statement: [Test of English as a Foreign Language, registrationMethod, online registration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: registrationMethod Context triple: [Test of English as a Foreign Language, registrationMethod, online registration]
-
A.
registrationMode
chosen
Indicates the method or process by which something is registered or enrolled.
-
B.
register
Indicates that an entity formally records or enrolls another entity or itself in an official system, list, or record.
-
C.
registrationCategory
Indicates the classification or type under which an entity is formally registered within a system or registry.
-
D.
registrationSuffix
Indicates the trailing part or extension added to a base registration identifier to form a complete registration code.
-
E.
confirmationMethod
Indicates the means or process by which something is verified, validated, or confirmed as true or accepted.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69a493406c408190957eeec9048a8fb6 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a0aebde88190a49d421477713103 |
completed | March 1, 2026, 8:25 p.m. |
| PD | Predicate disambiguation | batch_69a49d221d38819083c0adda81f59b07 |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.