Triple
T18884732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dosco |
E461929
|
entity |
| Predicate | informalTermFor |
P128317
|
FINISHED |
| Object | graduate of The Doon School |
—
|
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: graduate of The Doon School | Statement: [Dosco, informalTermFor, graduate of The Doon School]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: informalTermFor Context triple: [Dosco, informalTermFor, graduate of The Doon School]
-
A.
usedInformallyAlongside
Indicates that something is employed in an informal, non-standard way together with or in addition to something else.
-
B.
languageTerm
Indicates that one entity is a linguistic expression (word, phrase, or term) used to denote or label the other entity.
-
C.
typicalTerm
Indicates that something is a standard, representative, or characteristic term typically associated with a given concept or context.
-
D.
colloquialNameOf
chosen
Indicates that one entity is an informal, colloquial, or commonly used name referring to another entity.
-
E.
informalNotation
Indicates that an entity is represented or expressed using a non-standard, simplified, or colloquial form of notation rather than a formal or fully rigorous one.
- 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_69d8dcfc3430819095ee6fc0eb4c06a5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c3d53e608190b8740c092b6e1523 |
completed | April 20, 2026, 6:12 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e27e1481908a8da10b28f07875 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:57 a.m.