Triple
T38059746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shanwick Oceanic FIR |
E950306
|
entity |
| Predicate | trackSystemType |
P191627
|
FINISHED |
| Object | Daily optimized tracks |
—
|
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: Daily optimized tracks | Statement: [Shanwick Oceanic FIR, trackSystemType, Daily optimized tracks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trackSystemType Context triple: [Shanwick Oceanic FIR, trackSystemType, Daily optimized tracks]
-
A.
rackSystemType
Indicates the specific configuration or category of rack system associated with an entity.
-
B.
trackSystem
Indicates a relationship where one entity monitors, records, or follows the status, behavior, or changes of another entity within a system.
-
C.
trackType
Indicates the specific kind or category of track associated with an entity, such as its functional or physical classification.
-
D.
rootSystemType
Indicates the type or classification of an entity’s root system (e.g., taproot, fibrous, adventitious).
-
E.
systemType
Indicates the classification or category of a system that an entity belongs to or operates as.
- 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_69f76f01e63c819093b6012fc974f35a |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
| PDg | Predicate description generation | batch_69fce28a74508190aab36551094e8226 |
completed | May 7, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:21 p.m.