Triple
T6174907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leo |
E137793
|
entity |
| Predicate | bestVisibility |
P9694
|
FINISHED |
| Object | spring in Northern Hemisphere |
—
|
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: spring in Northern Hemisphere | Statement: [Leo, bestVisibility, spring in Northern Hemisphere]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bestVisibility Context triple: [Leo, bestVisibility, spring in Northern Hemisphere]
-
A.
visibleAt
chosen
Indicates that one entity can be seen or perceived from a specific location, viewpoint, or context at a given time.
-
B.
bestObservedWith
Indicates that one entity is most effectively or appropriately observed, detected, or measured when used or considered together with another specified entity.
-
C.
isEasierToSeeThan
Indicates that one entity is more visually noticeable or discernible than another under comparable viewing conditions.
-
D.
maximumBrightness
Indicates the highest level of brightness that an entity can reach or exhibit.
-
E.
canBeSeenWith
Indicates that two entities are observable together in the same context, setting, or time.
- 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_69c008a80f748190ba3d07ffc81acb29 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05dc55b5c819084482b735771c9a8 |
completed | March 22, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69c055f7f12881908e21c04e9b752ba4 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:18 p.m.