Triple
T202645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tropic of Cancer |
E4538
|
entity |
| Predicate | marksBoundaryOf |
P6131
|
FINISHED |
| Object | tropical zone |
—
|
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: tropical zone | Statement: [Tropic of Cancer, marksBoundaryOf, tropical zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marksBoundaryOf Context triple: [Tropic of Cancer, marksBoundaryOf, tropical zone]
-
A.
hasBoundaryFeature
chosen
Indicates that a boundary (such as an edge, border, or limit) of one entity is characterized, marked, or defined by a specific feature or element.
-
B.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
C.
borderStraddling
Indicates that something (such as a feature, structure, or area) extends across and occupies territory on both sides of a border between two regions or jurisdictions.
-
D.
hasBoundaryType
Indicates that one entity has a boundary characterized by a specific type or classification in relation to another entity or context.
-
E.
demarcationType
Indicates the specific way in which a boundary or separation between entities is defined, marked, or categorized.
- 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_69a25737567c81908f9c505300239181 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25f46b4f081909e5ee3718109a71f |
completed | Feb. 28, 2026, 3:21 a.m. |
| PD | Predicate disambiguation | batch_69a25b4b42ec8190bef16bbbdd30a742 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:51 a.m.