Triple
T31761753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brochis |
E810697
|
entity |
| Predicate | originHemisphere |
P177765
|
FINISHED |
| Object | Western Hemisphere |
—
|
NE NERFINISHED |
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: Western Hemisphere | Statement: [Brochis, originHemisphere, Western Hemisphere]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originHemisphere Context triple: [Brochis, originHemisphere, Western Hemisphere]
-
A.
hemisphereName
Indicates the named hemisphere (e.g., northern, southern, eastern, or western) that a given location or entity belongs to.
-
B.
liesInHemisphere
chosen
Indicates that one geographic entity is located within a specified hemisphere of the Earth.
-
C.
hemisphereSpecificity
Indicates that the relationship, property, or effect applies specifically to one cerebral hemisphere (left or right) rather than bilaterally.
-
D.
centerOfOrigin
Indicates the place or region where something (such as a species, product, idea, or movement) originally began or was first developed.
-
E.
hasProgenyInHemisphere
Indicates that an entity has offspring or descendants located within a specified hemisphere.
- 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_69f348e340d48190b780fae618c51464 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a01203ac018819085d7c9abd8345b23 |
completed | May 11, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_6a011f3f149c819090749722da0e3413 |
completed | May 11, 2026, 12:13 a.m. |
Created at: April 30, 2026, 11:31 p.m.