Triple
T8200507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loyalty Ridge |
E191557
|
entity |
| Predicate | hasLocationUncertainty |
P22067
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Loyalty Ridge, hasLocationUncertainty, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocationUncertainty Context triple: [Loyalty Ridge, hasLocationUncertainty, true]
-
A.
hasUncertainty
Indicates that the relationship or value is associated with some level or type of uncertainty rather than being fully definite or precise.
-
B.
hasApproximateLocation
chosen
Indicates that an entity is associated with a location that is known only imprecisely or within a general area rather than an exact position.
-
C.
hasLocationComponent
Indicates that something includes, is associated with, or is composed of a specific location-related part or element.
-
D.
possibleLocation
Indicates that an entity may be located at, or could plausibly occur in, a specified place or spatial context.
-
E.
hasLocationRole
Indicates that an entity holds or plays a specific role in relation to a particular location (e.g., origin, destination, storage site, or operational area).
- 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_69ca82c6e9548190a4c5ca14516e4417 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb5df565dc819099537fc06b694b40 |
completed | March 31, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69cb36aac86081909b83636e352e0ced |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:43 p.m.