Triple
T30057534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NORTA |
E763772
|
entity |
| Predicate | hasPlanningTool |
P99834
|
FINISHED |
| Object | online trip planner |
—
|
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: online trip planner | Statement: [NORTA, hasPlanningTool, online trip planner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlanningTool Context triple: [NORTA, hasPlanningTool, online trip planner]
-
A.
hasPlanningInstrument
Indicates that an entity is associated with, or governed by, a specific planning instrument (such as a plan, policy, or regulatory document) that guides its development or management.
-
B.
managementPlanningTool
chosen
Indicates that an entity is a tool or system used to support, organize, or execute management planning activities for another entity or process.
-
C.
hasPlanner
Indicates that an entity is associated with or assigned a planner responsible for organizing or managing its activities or processes.
-
D.
hasPlanningFunction
Indicates that an entity is responsible for or involved in planning, organizing, or determining future actions or strategies.
-
E.
hasPlanningType
Indicates that an entity is associated with a specific category or type used for planning or scheduling purposes.
- 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_69f224716378819087a722e487832b70 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: April 29, 2026, 6:56 p.m.