Triple
T20847342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amphitheatre Terrace |
E513262
|
entity |
| Predicate | hasChairs |
P142075
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Amphitheatre Terrace, hasChairs, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChairs Context triple: [Amphitheatre Terrace, hasChairs, yes]
-
A.
hasChairCount
Indicates the number of chairs associated with a given entity.
-
B.
chairAlsoChairs
Indicates that an entity who chairs one group, meeting, or committee also serves as the chair of another.
-
C.
coChairWith
Indicates that two or more entities share the role of chairing the same group, event, or organization jointly.
-
D.
hasSuspendedChairs
Indicates that one entity features or contains chairs that are hanging or suspended rather than resting directly on the floor.
-
E.
canChair
Indicates that an entity has the authority or capability to preside over, lead, or chair a meeting, committee, or similar group.
- F. None of above. chosen
Provenance (4 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_69e0b4f4898081908209e58edb8f9c45 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c351300c8190a4ec2eb430f0c23d |
completed | April 21, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a593f481908beb457c29f1ce73 |
completed | April 20, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e5d53c4d6881909b4d0a716fa5ed4a |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 16, 2026, 12:43 p.m.