Triple
T23465265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gotham City Sirens |
E569085
|
entity |
| Predicate | hasSpinOffOrRelatedTeam |
P7226
|
FINISHED |
| Object | Birds of Prey |
—
|
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: Birds of Prey | Statement: [Gotham City Sirens, hasSpinOffOrRelatedTeam, Birds of Prey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpinOffOrRelatedTeam Context triple: [Gotham City Sirens, hasSpinOffOrRelatedTeam, Birds of Prey]
-
A.
spinOffTeam
Indicates that a new team has been created by separating or branching off from an existing team.
-
B.
hasSpinOff
chosen
Indicates that one entity is a derivative or spin-off product, work, or organization that originated from another entity.
-
C.
hasFranchiseOrSpinOff
Indicates that one work, series, or product is related to another as a franchise entry or a spin-off derived from it.
-
D.
hasSubteam
Indicates that one team is a subordinate or component team within another, larger team.
-
E.
relatedTeam
Indicates that two teams are connected or associated with each other in a relevant or meaningful way.
- 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_69e2458ebd808190b3298163132cfb0b |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a6f9e59081909e8cf224ee46109c |
completed | April 29, 2026, 6:36 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:54 p.m.