Triple
T23244518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 畢宿五 |
E581546
|
entity |
| Predicate | 在導航中的作用 |
P11421
|
FINISHED |
| Object | 可作為天文導航亮星參考 |
—
|
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: 可作為天文導航亮星參考 | Statement: [畢宿五, 在導航中的作用, 可作為天文導航亮星參考]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 在導航中的作用 Context triple: [畢宿五, 在導航中的作用, 可作為天文導航亮星參考]
-
A.
navigationRole
Indicates that one entity serves as a navigational aid, control, or function that helps users move through or orient themselves within another entity (such as an interface, document, or environment).
-
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.
navigation
Indicates the act or process of determining and following a path or route from one location or state to another.
-
D.
hasNavigationAid
Indicates that one entity provides or is equipped with a navigation aid used to assist in determining position or direction.
-
E.
hasNavigationPurpose
Indicates that something exists or is designed specifically to serve a navigational function or goal.
- 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_69e24606b17c81908aba1a4911c8a8ba |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f193ee37c8819091f799506fa532da |
completed | April 29, 2026, 5:15 a.m. |
| PD | Predicate disambiguation | batch_69effce4d704819092826931d430e8c4 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:10 p.m.