Triple
T20511000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orsay Lighthouse |
E503559
|
entity |
| Predicate | navigationalPurpose |
P84544
|
FINISHED |
| Object | aid to navigation |
—
|
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: aid to navigation | Statement: [Orsay Lighthouse, navigationalPurpose, aid to navigation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navigationalPurpose Context triple: [Orsay Lighthouse, navigationalPurpose, aid to navigation]
-
A.
hasNavigationPurpose
chosen
Indicates that something exists or is designed specifically to serve a navigational function or goal.
-
B.
routePurpose
Indicates the intended function or goal that a particular route is designed or used to serve.
-
C.
navigation
Indicates the act or process of determining and following a path or route from one location or state to another.
-
D.
usedToNavigate
Indicates that one entity served as a means or tool for another entity to find or follow a route or direction.
-
E.
navigability
Indicates how easily and effectively something (such as a space, interface, or route) can be traversed or moved through.
- 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_69e0b4b2aa788190ae9eb37c1d73b1f1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69dcb8f5c8190b0d4c09f3669a8ec |
completed | April 20, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69e59fdb7ad88190924176c32a195db3 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:36 a.m.