Triple
T2010744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miles of Aisles |
E43682
|
entity |
| Predicate | hasLiveSpokenIntroductions |
P34457
|
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: [Miles of Aisles, hasLiveSpokenIntroductions, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLiveSpokenIntroductions Context triple: [Miles of Aisles, hasLiveSpokenIntroductions, yes]
-
A.
hasSpokenAbout
Indicates that one entity has verbally expressed, discussed, or mentioned another entity or topic.
-
B.
spokenBefore
Indicates that one entity has spoken or produced speech earlier in time than another entity.
-
C.
hasSpeakersIn
Indicates that an entity (such as an event, conference, or session) includes or is associated with speakers located in or belonging to a specified place or group.
-
D.
hasMainSpeaker
Indicates that one entity serves as the primary or principal speaker associated with another entity, such as an event, recording, or presentation.
-
E.
spokeAt
Indicates that a person delivered a talk, speech, or presentation at a particular event or location.
- 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_69a88716e9f08190946313fdc949e3cf |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb8afe6f8819092679c86d1f2d041 |
completed | March 7, 2026, 5:33 a.m. |
| PD | Predicate disambiguation | batch_69abb7a03a1c81909ad50d56667db2d5 |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb83e7888819096dc40275c77daff |
completed | March 7, 2026, 5:31 a.m. |
Created at: March 4, 2026, 7:37 p.m.