Triple
T24872493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ponyboy Curtis |
E622472
|
entity |
| Predicate | hasRivalGroup |
P17627
|
FINISHED |
| Object | the Socs |
—
|
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: the Socs | Statement: [Ponyboy Curtis, hasRivalGroup, the Socs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRivalGroup Context triple: [Ponyboy Curtis, hasRivalGroup, the Socs]
-
A.
hasForeignRival
Indicates that an entity has at least one rival that is based in or originates from a different country or foreign jurisdiction.
-
B.
hasRivalryAspect
Indicates that there exists a competitive or adversarial relationship or dimension between entities.
-
C.
hasRivalryCategory
Indicates that there exists a competitive or adversarial relationship between entities that falls into a specific classified type or category of rivalry.
-
D.
hasRivalStand
Indicates that one entity maintains a competing or opposing stand, position, or operation in relation to another entity.
-
E.
hasAntagonistGroup
chosen
Indicates that an entity is opposed or challenged by a specific group acting as its antagonist.
- 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_69e2fac3fdbc81909c2ec49be5743cd9 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d6ef33081908f5d36ba1ae5f473 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 5:23 a.m.