Triple
T32932341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Heights |
E842430
|
entity |
| Predicate | hasInUniverseRegionType |
P174654
|
FINISHED |
| Object | small city |
—
|
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: small city | Statement: [River Heights, hasInUniverseRegionType, small city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInUniverseRegionType Context triple: [River Heights, hasInUniverseRegionType, small city]
-
A.
inUniverseRegion
Indicates that an entity is located within or belongs to a specific universe-defined region or area.
-
B.
isPartOfRegionType
chosen
Indicates that one region belongs to, or is classified under, a broader region type or category.
-
C.
inUniverseLocationType
Indicates the type or category of location that something occupies within a fictional or defined universe or setting.
-
D.
containsRegionType
Indicates that one region includes or encompasses another region of a specified type within its spatial or logical boundaries.
-
E.
hasInUniverseLocationRelation
Indicates a relationship where an entity is associated with, or situated at, a specific location within a fictional or defined universe or setting.
- 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_69f34948adfc8190a937f1f622783c0b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ffbf84f4948190b41a7bba07ae61ec |
completed | May 9, 2026, 11:13 p.m. |
| PD | Predicate disambiguation | batch_69ffbf0a59f88190870dbe25d8a63a00 |
completed | May 9, 2026, 11:11 p.m. |
Created at: May 1, 2026, 1:20 a.m.