Triple
T24397679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crossroads |
E615071
|
entity |
| Predicate | liveArrangementBy |
P48738
|
FINISHED |
| Object | Cream |
—
|
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: Cream | Statement: [Crossroads, liveArrangementBy, Cream]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liveArrangementBy Context triple: [Crossroads, liveArrangementBy, Cream]
-
A.
hasLiveArrangement
Indicates that there is an active, ongoing arrangement or agreement currently in effect between the related entities.
-
B.
livePerformanceFeature
chosen
Indicates that one entity is included or highlighted as a component of another entity’s live performance.
-
C.
arranges
Indicates that one entity organizes, coordinates, or puts in order some event, objects, or circumstances involving another entity.
-
D.
livePerformanceStapleFor
Indicates that something (such as a song or piece) is regularly and prominently featured in another entity’s live performances.
-
E.
commonlyArrangedFor
Indicates that one entity is typically organized, scheduled, or set up on behalf of 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_69e2d7e509b88190a53155d4f3de45ce |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f294d85db08190b4c63ea6b7b74438 |
completed | April 29, 2026, 11:31 p.m. |
| PD | Predicate disambiguation | batch_69f287c4a2b48190b80fb7a3c0e9b018 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:04 a.m.