Triple
T2387845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elm |
E48867
|
entity |
| Predicate | hasSettlementHierarchyLevel |
P275
|
FINISHED |
| Object | village in Cambridgeshire |
—
|
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: village in Cambridgeshire | Statement: [Elm, hasSettlementHierarchyLevel, village in Cambridgeshire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSettlementHierarchyLevel Context triple: [Elm, hasSettlementHierarchyLevel, village in Cambridgeshire]
-
A.
hasLegalHierarchy
Indicates that one entity holds a higher or subordinate legal status, authority, or jurisdiction in relation to another within a formal legal structure.
-
B.
hasNumberOfLevels
Indicates that an entity possesses a specified count of distinct levels or tiers.
-
C.
hasDivisionLevel
chosen
Indicates that one entity is associated with a specific hierarchical or organizational division level of another entity.
-
D.
hasMultipleLevels
Indicates that something is organized into more than one hierarchical or structural level.
-
E.
isPartOfHierarchyWith
Indicates that one entity occupies a defined position within an ordered or nested structure relative to another entity in the same hierarchy.
- 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_69a88aa5f63081908d07fd302029fcbd |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc7db4ee08190a5c114e42bc46f70 |
completed | March 7, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_69abc5a1b5748190b4cd8989700f4dd2 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:57 p.m.