Triple
T27106308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richland Balsam |
E686587
|
entity |
| Predicate | hasOverlookName |
P161856
|
FINISHED |
| Object | Richland Balsam Overlook |
—
|
NE NERFINISHED |
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: Richland Balsam Overlook | Statement: [Richland Balsam, hasOverlookName, Richland Balsam Overlook]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOverlookName Context triple: [Richland Balsam, hasOverlookName, Richland Balsam Overlook]
-
A.
hasCoverName
Indicates that one entity uses or is known by an alternative, often secret or assumed, name in relation to another entity or context.
-
B.
hasNameGivenTo
Indicates that one entity is the name that has been assigned or given to another entity.
-
C.
hasGivenNameOfOwner
Indicates that an entity is associated with the given (first) name of its owner.
-
D.
hasNameCharacteristic
Indicates that an entity possesses a specific quality or attribute related to its name.
-
E.
hasGivenNameUsage
Indicates that an entity is associated with a particular way or context in which its given name is used.
- 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_69ef148accd48190b6ed6e13a15f2a4f |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f623fdda548190827d6867bba39de7 |
completed | May 2, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69f61b40f02081909bd9c3ea73249163 |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61fa35ac48190890102c348ed81a0 |
completed | May 2, 2026, 4 p.m. |
Created at: April 27, 2026, 8:50 a.m.