Triple
T28639122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Golden Snitch |
E724870
|
entity |
| Predicate | positionThatSeeksIt |
P192135
|
FINISHED |
| Object | Seeker |
—
|
LITERAL FINISHED |
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: Seeker | Statement: [Golden Snitch, positionThatSeeksIt, Seeker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionThatSeeksIt Context triple: [Golden Snitch, positionThatSeeksIt, Seeker]
-
A.
positionSought
Indicates the specific role, job, or position that an entity is aiming to obtain or apply for.
-
B.
targetedPosition
Indicates a relationship where an action, influence, or focus is specifically directed toward a particular position, role, or location.
-
C.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
D.
positionAt
Indicates that one entity is located at, or occupies, a specific spatial position relative to another entity or reference frame.
-
E.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
- F. None of above. chosen
Provenance (4 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_69f01d8328c48190bc0e5f9b9b848582 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
| PDg | Predicate description generation | batch_69fcf82405c88190a19cecf8e9cc272d |
completed | May 7, 2026, 8:37 p.m. |
Created at: April 28, 2026, 4:43 a.m.