Triple
T32049753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alden Pyle |
E818455
|
entity |
| Predicate | rivalryOver |
P97674
|
FINISHED |
| Object | Phuong |
—
|
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: Phuong | Statement: [Alden Pyle, rivalryOver, Phuong]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rivalryOver Context triple: [Alden Pyle, rivalryOver, Phuong]
-
A.
rivalryBasis
Indicates the underlying reason, cause, or grounds on which a rivalry between entities is based.
-
B.
rivalryCharacterizedBy
Indicates a relationship where a rivalry is defined or distinguished by a particular feature, quality, or circumstance.
-
C.
rivalryFocus
chosen
Indicates a relationship in which one entity is the primary target or center of another entity’s competitive or adversarial rivalry.
-
D.
rivalryLevel
Indicates the degree or intensity of competitive opposition or conflict between two entities.
-
E.
involvesRivalryBetween
Indicates a relationship in which two or more entities are engaged in rivalry or competitive opposition with one another.
- 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_69f348fcfb648190859f6be5e04b7cfe |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b4c884148190be2cb7d9b354d17f |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b154b3dc819087115f5f63f7b00f |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:20 a.m.