Triple
T9796421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | India Plate |
E237727
|
entity |
| Predicate | pastEnvironment |
P17620
|
FINISHED |
| Object | once located in the Southern 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: once located in the Southern Hemisphere | Statement: [India Plate, pastEnvironment, once located in the Southern Hemisphere]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pastEnvironment Context triple: [India Plate, pastEnvironment, once located in the Southern Hemisphere]
-
A.
formerHabitat
chosen
Indicates that a location once served as a habitat for an entity but no longer does.
-
B.
secondaryEnvironment
Indicates that an entity is associated with an additional or supporting environment distinct from its primary one.
-
C.
previousCircumscription
Indicates that one entity served as an earlier or prior version, scope, or boundary definition of another entity.
-
D.
pastOrdinary
Indicates that the related action or state occurred in the past using the simple (non-progressive, non-perfect) tense.
-
E.
environmentalPersistence
Indicates how long or to what extent something remains present, active, or effective in an environment after its initial introduction.
- 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_69ca84dc04488190b9c91193976c0960 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda34a53548190a8cb524381fe2bf9 |
completed | April 1, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69cd03da45a88190b71b1be3354c15a6 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:28 p.m.