Triple
T27686553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eric Sacks (Teenage Mutant Ninja Turtles 2014) |
E698046
|
entity |
| Predicate | secretAllegiance |
P91605
|
FINISHED |
| Object | Foot Clan |
—
|
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: Foot Clan | Statement: [Eric Sacks (Teenage Mutant Ninja Turtles 2014), secretAllegiance, Foot Clan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secretAllegiance Context triple: [Eric Sacks (Teenage Mutant Ninja Turtles 2014), secretAllegiance, Foot Clan]
-
A.
secretAffiliation
chosen
Indicates a hidden or undisclosed association, membership, or allegiance that one entity has with another.
-
B.
secretRevealed
Indicates that previously hidden or confidential information has been disclosed to one or more parties.
-
C.
hadAllegiance
Indicates that an entity was loyally committed or formally bound in support or service to another entity, such as a person, group, or cause.
-
D.
namedForAllegiance
Indicates that an entity is named in reference to, or in honor of, a particular allegiance, affiliation, or loyalty.
-
E.
allegianceArc
Indicates a change or evolution in an entity’s loyalty or allegiance to another entity over time.
- 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_69ef590df8708190af5488f0638e790c |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6359e3d3c81909814e2f0a7fb0ea9 |
completed | May 2, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f631871c888190bf29466fe4254e51 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 2:49 p.m.