Triple
T13749299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theodore Unit |
E330298
|
entity |
| Predicate | collaboratedOnRelease |
P110826
|
FINISHED |
| Object | 718 |
—
|
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: 718 | Statement: [Theodore Unit, collaboratedOnRelease, 718]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collaboratedOnRelease Context triple: [Theodore Unit, collaboratedOnRelease, 718]
-
A.
hasCollaboratedIn
Indicates that two or more entities have worked together on a shared project, task, or activity.
-
B.
workedOnAlbum
Indicates that an entity contributed work or effort to the creation or production of a particular music album.
-
C.
publishedInCollaborationWith
Indicates that an entity was published as a result of a joint effort or partnership with another entity.
-
D.
notableCollaboration
Indicates a significant joint effort or partnership between entities that produced a noteworthy shared outcome or work.
-
E.
alsoReleased
Indicates that two or more items were released at the same time or as part of the same release event.
- 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_69d81c573f288190aa2403d484fa3d49 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02148c208190a882927905a861a6 |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbbe950b148190ba0df8a749269ec6 |
completed | April 12, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69dbc59db0148190bcaf9646403ca64f |
completed | April 12, 2026, 4:17 p.m. |
Created at: April 9, 2026, 10:08 p.m.