Triple
T20186495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quidditch pitch |
E492873
|
entity |
| Predicate | hasGoalStructure |
P139027
|
FINISHED |
| Object | three hoops at each end |
—
|
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: three hoops at each end | Statement: [Quidditch pitch, hasGoalStructure, three hoops at each end]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGoalStructure Context triple: [Quidditch pitch, hasGoalStructure, three hoops at each end]
-
A.
goalStructure
Indicates the overarching objective or intended outcome that organizes and guides the structure of related actions, components, or relationships.
-
B.
hasPlanningGoal
Indicates that an entity is associated with, or directed toward achieving, a specific planning objective or target state.
-
C.
hasProgramGoal
Indicates that an entity (such as a program or initiative) is associated with a specific intended goal or objective it aims to achieve.
-
D.
hasPrimaryGoal
Indicates that an entity’s main or most important objective is the specified goal.
-
E.
hasOperationalGoal
Indicates that an entity is associated with a specific objective or target it aims to achieve through its operations or activities.
- 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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66ad143c48190b9d52c331e8101d6 |
completed | April 20, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_69e55b11124c8190babacf2a0fe2d057 |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56700b1a08190ace53cf95827d72d |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 11, 2026, 11:36 p.m.