Triple
T35807386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edge and Christian |
E1035134
|
entity |
| Predicate | teammateRingName |
P184141
|
FINISHED |
| Object | Edge |
—
|
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: Edge | Statement: [Edge and Christian, teammateRingName, Edge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teammateRingName Context triple: [Edge and Christian, teammateRingName, Edge]
-
A.
ringName
Indicates that a ring is identified or referred to by a specific name.
-
B.
ringNameOf
Indicates that one entity is the name or designation assigned to a particular ring (such as a ring structure, ring system, or ring object).
-
C.
ringNameUser
chosen
Indicates that a user is associated with or identified by a particular ring name (e.g., a nickname or alias used within a ring or group).
-
D.
hasRingName
Indicates that an entity is associated with, or designated by, a specific ring name.
-
E.
originalRingName
Indicates the name originally used for a ring before any later changes or renamings.
- 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ac23d1388190bdf9628b294943bd |
completed | May 3, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f7ab734d848190a84f9b8c3a952b75 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:06 p.m.