Triple
T23244504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 畢宿五 |
E581546
|
entity |
| Predicate | 自行 |
P20805
|
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.
selfDetermination
Indicates that an entity independently determines its own course of action, decisions, or status without external control or imposition.
-
B.
autonomousFor
Indicates that one entity operates or makes decisions independently on behalf of, or in place of, another specified context, system, or agent.
-
C.
selfSustainment
Indicates that an entity is able to maintain its own operation or existence over time using its internal resources or capabilities, without requiring external support.
-
D.
canActOnOwnInitiative
chosen
Indicates that an entity is capable of initiating actions independently, without requiring external prompts or directives.
-
E.
organizedIndependentlyOf
Indicates that an entity was organized or formed without direction, control, or coordination from another specified entity.
- 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_69effcdadec0819092ec1749ee453b4e |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:10 p.m.