Triple
T38206061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maine 4000 Footers (near-4000 category) |
E1009202
|
entity |
| Predicate | goalForParticipants |
P32840
|
FINISHED |
| Object | visit all listed near-4000-foot peaks |
—
|
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: visit all listed near-4000-foot peaks | Statement: [Maine 4000 Footers (near-4000 category), goalForParticipants, visit all listed near-4000-foot peaks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goalForParticipants Context triple: [Maine 4000 Footers (near-4000 category), goalForParticipants, visit all listed near-4000-foot peaks]
-
A.
goalsFor
Indicates the number of goals scored by one participant or team in favor of a particular side or match context.
-
B.
goalIn
Indicates that one entity’s objective, aim, or intended outcome is located within, directed toward, or achieved inside another entity or context.
-
C.
goalType
Indicates the specific category or nature of a goal associated with an entity or action.
-
D.
goals
Indicates that an entity has objectives, targets, or desired outcomes it aims to achieve.
-
E.
statedAsGoalFor
chosen
Indicates that something has been explicitly declared or identified as a goal for a particular entity or context.
- 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_69f76dc94fcc8190bd2f55e81f9d6527 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:30 p.m.