Triple
T5637012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beta Crucis |
E147971
|
entity |
| Predicate | isUsedForNavigation |
P11421
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Beta Crucis, isUsedForNavigation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUsedForNavigation Context triple: [Beta Crucis, isUsedForNavigation, true]
-
A.
hasNavigationUse
Indicates that something is used for navigation or serves a navigational function in relation to another entity.
-
B.
usedToNavigate
chosen
Indicates that one entity served as a means or tool for another entity to find or follow a route or direction.
-
C.
isNavigationStar
Indicates that one entity serves as a guiding or reference star used for navigation relative to another entity.
-
D.
navigableFor
Indicates that one entity (such as a path, route, or medium) can be traversed or used for movement by another entity (such as a vehicle, vessel, or agent).
-
E.
hasNavigationCharacteristic
Indicates that an entity possesses a specific property, feature, or quality related to navigation or navigational behavior.
- 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_69c00907bc8881909ed760d3ed73ef35 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c022809f708190ab859aa446683b10 |
completed | March 22, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69c01b1f12ec8190b4b9d9ee31cabe19 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:41 p.m.