Triple
T29304616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MIT Building 10 |
E743056
|
entity |
| Predicate | isRecognizableBy |
P99189
|
FINISHED |
| Object | Great Dome |
—
|
NE NERFINISHED |
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: Great Dome | Statement: [MIT Building 10, isRecognizableBy, Great Dome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRecognizableBy Context triple: [MIT Building 10, isRecognizableBy, Great Dome]
-
A.
recognizableFor
chosen
Indicates that one entity is known or identifiable because of a particular characteristic, feature, or association with another entity.
-
B.
areRecognizedBy
Indicates that one entity acknowledges, identifies, or accepts another entity as valid, known, or legitimate.
-
C.
canRecognize
Indicates that one entity has the ability to identify or distinguish another entity based on its features or characteristics.
-
D.
recognizableWhen
Indicates that one entity can be correctly identified or distinguished under the conditions, context, or representation specified by another entity.
-
E.
recognizedFor
Indicates that one entity is acknowledged, credited, or honored for a particular achievement, quality, contribution, or work associated with another entity.
- 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_69f09123ed9881909f351f7541933f5e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f665a5724c8190b3c31ea61745a426 |
completed | May 2, 2026, 8:59 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 1:12 p.m.