Triple
T5380180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | W43 star-forming complex |
E113061
|
entity |
| Predicate | inGalacticQuadrant |
P63648
|
FINISHED |
| Object | first Galactic quadrant |
—
|
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 Galactic quadrant | Statement: [W43 star-forming complex, inGalacticQuadrant, first Galactic quadrant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inGalacticQuadrant Context triple: [W43 star-forming complex, inGalacticQuadrant, first Galactic quadrant]
-
A.
galacticQuadrantCoverage
Indicates the extent to which a given entity’s area of responsibility, influence, or operation spans one or more specified galactic quadrants.
-
B.
galacticDestination
Indicates that one entity serves as the target or endpoint location within a galaxy that another entity is directed or traveling toward.
-
C.
isInGalaxy
Indicates that one astronomical object is located within or belongs to a particular galaxy.
-
D.
hostGalaxyConstellation
Indicates the constellation in which the host galaxy of an object is located.
-
E.
targetGalaxy
Indicates that one entity is the galaxy toward which another entity is directed, aimed, or focused.
- 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_69bd4436a1988190af18dcff7fd306b4 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd88801b188190b9ac35ed89167fa3 |
completed | March 20, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69bd846172788190969f24bc7503c05e |
completed | March 20, 2026, 5:31 p.m. |
| PDg | Predicate description generation | batch_69bd887f5b0081909456992d1a071928 |
completed | March 20, 2026, 5:48 p.m. |
Created at: March 20, 2026, 2:03 p.m.