Triple
T19174303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | flag of Brazil |
E469400
|
entity |
| Predicate | starArrangementPerspective |
P134721
|
FINISHED |
| Object | viewed from outside the celestial sphere |
—
|
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: viewed from outside the celestial sphere | Statement: [flag of Brazil, starArrangementPerspective, viewed from outside the celestial sphere]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: starArrangementPerspective Context triple: [flag of Brazil, starArrangementPerspective, viewed from outside the celestial sphere]
-
A.
starsPosition
Indicates that one entity specifies the spatial location or coordinates of a star or group of stars relative to a reference frame.
-
B.
starPosition
Indicates the spatial location or coordinates of a star relative to a defined reference frame.
-
C.
positionInAsterism
Indicates the specific location or role that an object occupies within a defined asterism pattern.
-
D.
isAsterismOf
Indicates that one or more stars collectively form or belong to a specific asterism.
-
E.
starType
Indicates the classification relationship specifying what type or category of star an astronomical object is.
- F. None of above. chosen
Provenance (4 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_69d8dd09d5a081909ae43c286651ae5a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f16613dc8190987c2d79dc616e40 |
completed | April 20, 2026, 9:27 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b83d6881908e6271c620f74100 |
completed | April 19, 2026, 11:17 a.m. |
| PDg | Predicate description generation | batch_69e4bfe9ef7081908a74a57d1fc731ea |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:06 p.m.