Triple
T32387047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quest for the Heavens |
E827569
|
entity |
| Predicate | moduleRole |
P40371
|
FINISHED |
| Object | first laboratory module of Tiangong |
—
|
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: first laboratory module of Tiangong | Statement: [Quest for the Heavens, moduleRole, first laboratory module of Tiangong]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: moduleRole Context triple: [Quest for the Heavens, moduleRole, first laboratory module of Tiangong]
-
A.
unitRole
chosen
Indicates the functional role or purpose that a unit serves within a larger system or context.
-
B.
roleComponent
Indicates that one entity functions as a component or constituent part within the role or capacity defined by another entity.
-
C.
libraryRole
Indicates the specific function, responsibility, or position an entity holds within the context of a library.
-
D.
MCURole
Indicates a role or function that an entity holds as a Master of Ceremonies (MC) within an event or context.
-
E.
massRole
Indicates that an entity plays a specific role or function within a mass or collective context.
- 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_69f349184e7481909c6c54428cb9cf12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c1d325308190a1dc982b40203152 |
completed | May 3, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:51 a.m.