Triple
T35325280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Everyday Rapture |
E1020162
|
entity |
| Predicate | hasOrchestrationsBy |
P34454
|
FINISHED |
| Object | Tom Kitt |
—
|
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: Tom Kitt | Statement: [Everyday Rapture, hasOrchestrationsBy, Tom Kitt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrchestrationsBy Context triple: [Everyday Rapture, hasOrchestrationsBy, Tom Kitt]
-
A.
hasOrchestrationBy
chosen
Indicates that something is organized, coordinated, or arranged by a specified agent or entity.
-
B.
hasOrchestration
Indicates that one entity coordinates, manages, or sequences the actions or interactions of another entity or set of entities.
-
C.
hasOrchestrationCompletedBy
Indicates that an orchestration process has been fully completed by a specified agent or system.
-
D.
usesOrchestrationSimilarTo
Indicates that one entity employs an orchestration approach or mechanism that is similar to that used by another entity.
-
E.
usesOrchestration
Indicates that one entity employs orchestration mechanisms or tools to coordinate, manage, or automate the behavior and interactions of other entities or processes.
- 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_69f76deacf4481908e7735a5a7715b0a |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fec00f27988190955de6b6348a4d97 |
completed | May 9, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_69febd52037c8190b475dbd50fdbc13e |
completed | May 9, 2026, 4:51 a.m. |
Created at: May 3, 2026, 4:03 p.m.