Triple
T17886046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Teen Titans |
E447203
|
entity |
| Predicate | includesSidekicksOf |
P116472
|
FINISHED |
| Object | Justice League heroes |
—
|
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: Justice League heroes | Statement: [New Teen Titans, includesSidekicksOf, Justice League heroes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesSidekicksOf Context triple: [New Teen Titans, includesSidekicksOf, Justice League heroes]
-
A.
formerSidekick
Indicates that one entity previously served as a sidekick or subordinate companion to another entity, but no longer holds that role.
-
B.
hasFictionalSibling
Indicates that one entity is a fictional character who is a sibling of another entity.
-
C.
includesCompanion
chosen
Indicates that one entity involves, contains, or is accompanied by another entity acting as a companion.
-
D.
appearsAlongside
Indicates that two entities are present or occur together in the same context, setting, or instance.
-
E.
hasFictionalCoStar
Indicates that one entity appears as a co-star alongside another entity within a fictional work or narrative.
- 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_69d8b9f59bd48190a6fc925a855b8bac |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49c13bd288190a0302010ba4d0532 |
completed | April 19, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e9b77c8190bbfb508f28dfacfa |
completed | April 18, 2026, 7:18 p.m. |
Created at: April 10, 2026, 10:18 a.m.