Triple
T4618922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zodiac |
E100931
|
entity |
| Predicate | angularWidth |
P6952
|
FINISHED |
| Object | about 8 degrees north and south of the ecliptic |
—
|
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: about 8 degrees north and south of the ecliptic | Statement: [Zodiac, angularWidth, about 8 degrees north and south of the ecliptic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: angularWidth Context triple: [Zodiac, angularWidth, about 8 degrees north and south of the ecliptic]
-
A.
angularSize
chosen
Indicates the apparent size of an object as seen from a given point, typically measured as the angle it subtends at the observer.
-
B.
typicalWidth
Indicates the usual or characteristic width associated with an entity, as opposed to an exact or measured width in a specific instance.
-
C.
hasWidth
Indicates that an entity possesses a specific measurement or extent along its width dimension.
-
D.
minimumWidth
Indicates that there is a specified smallest allowable or required width for something in the relationship.
-
E.
widthInColumns
Indicates the number of column units that an element or item spans within a grid or layout.
- 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_69bd43cf363c819087fd5ab441b4a3f4 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59e247448190ad92f194cb1127c5 |
completed | March 20, 2026, 2:29 p.m. |
| PD | Predicate disambiguation | batch_69bd522fd5c48190ad2bffc0a5bc9061 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:12 p.m.