Triple
T19995887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Admiral’s Men |
E494190
|
entity |
| Predicate | usedPlayhouseType |
P16508
|
FINISHED |
| Object | amphitheatre |
—
|
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: amphitheatre | Statement: [Admiral’s Men, usedPlayhouseType, amphitheatre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedPlayhouseType Context triple: [Admiral’s Men, usedPlayhouseType, amphitheatre]
-
A.
usedTheatreFrom
Indicates that one entity made use of or operated within a particular theatre (such as a theater building, venue, or performance space) during some period or context.
-
B.
theatreType
chosen
Indicates the specific category or kind of theatre associated with an entity, such as its format, style, or operational model.
-
C.
theaterType
Indicates the specific kind or category of theater associated with an entity (e.g., cinema, opera house, drama theater).
-
D.
hasPlayType
Indicates the type or category of play associated with an event, action, or performance.
-
E.
usedInTheatre
Indicates that something is employed or applied within the context of a theatre or theatrical production.
- 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65fe3fb288190a935c334e8a5d54e |
completed | April 20, 2026, 5:18 p.m. |
| PD | Predicate disambiguation | batch_69e537fd311881908448f2aea8b4812e |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 11, 2026, 3:32 p.m.