Triple
T25001763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kevin Nash |
E625734
|
entity |
| Predicate | formedStableWith |
P130999
|
FINISHED |
| Object | Scott Hall |
—
|
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: Scott Hall | Statement: [Kevin Nash, formedStableWith, Scott Hall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formedStableWith Context triple: [Kevin Nash, formedStableWith, Scott Hall]
-
A.
formedStable
Indicates that a relationship, structure, or configuration has come into existence and remains consistently intact or unchanged over time.
-
B.
stabilizedBy
Indicates that an entity’s state, structure, or behavior is made more steady, secure, or resistant to change through the influence or support of another entity.
-
C.
isStable
Indicates that the state, condition, or configuration of an entity does not change significantly over time or under expected variations in its environment.
-
D.
associatedStable
chosen
Indicates that one entity is linked or connected to a particular stable in a way that denotes an ongoing or defined association.
-
E.
formedInState
Indicates that an entity was created, established, or officially organized within a particular state or subnational jurisdiction.
- 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_69e2ff26c50481908bc82e799c9e6587 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 18, 2026, 6:04 a.m.