Triple
T851467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Son bridge |
E18393
|
entity |
| Predicate | objectiveOf |
P5437
|
FINISHED |
| Object | Eindhoven corridor advance |
—
|
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: Eindhoven corridor advance | Statement: [Son bridge, objectiveOf, Eindhoven corridor advance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: objectiveOf Context triple: [Son bridge, objectiveOf, Eindhoven corridor advance]
-
A.
opponentObjective
Indicates that one entity is the target or goal that an opposing entity aims to counter, defeat, or prevent from succeeding.
-
B.
goals
Indicates that an entity has objectives, targets, or desired outcomes it aims to achieve.
-
C.
educationalObjective
Indicates the intended learning goal, skill, or competency that an educational resource, activity, or program is designed to achieve.
-
D.
strategicGoal
chosen
Indicates that one entity represents a long-term objective or desired outcome that another entity is intentionally aiming to achieve or align actions toward.
-
E.
aimsToSolve
Indicates an intention or purpose directed toward resolving, addressing, or eliminating a particular problem, challenge, or issue.
- 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_69a4938b04208190b82e1df6b572c548 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac22de288190913714d41e5a8e12 |
completed | March 1, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69a4aa81ef348190b067f817574e9efe |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.