Triple
T10957233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hippopotamus |
E258876
|
entity |
| Predicate | isLessTerritorial |
P96823
|
FINISHED |
| Object | on land |
—
|
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: on land | Statement: [Hippopotamus, isLessTerritorial, on land]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLessTerritorial Context triple: [Hippopotamus, isLessTerritorial, on land]
-
A.
hasTerritorialDimension
Indicates that something possesses or involves a spatial or territorial extent, scope, or jurisdiction.
-
B.
territorial
Indicates that one entity claims, defends, or is associated with control over a specific area or domain in relation to another entity.
-
C.
territorialAmbition
Indicates a desire or intent by one entity to expand its control, ownership, or influence over additional geographic areas or territories.
-
D.
appliesToTerritorialDisputes
Indicates that a rule, agreement, or condition is relevant to or governs situations involving territorial disputes between parties.
-
E.
reducedTerritoryOf
Indicates that one entity has caused a decrease in the size or extent of another entity's territory or area of control.
- F. None of above. chosen
Provenance (4 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_69d6aa88500c819097d7032ca578e74f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d771260e9881909401a7a7466e1b8a |
completed | April 9, 2026, 9:28 a.m. |
| PD | Predicate disambiguation | batch_69d72e874f48819096ffa878f90c7d5b |
completed | April 9, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69d7322370648190ba14cdd6fb4cdcb0 |
completed | April 9, 2026, 4:59 a.m. |
Created at: April 8, 2026, 9:23 p.m.