Triple
T23114986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Acla |
E576723
|
entity |
| Predicate | exactLocationKnown |
P150961
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Acla, exactLocationKnown, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exactLocationKnown Context triple: [Acla, exactLocationKnown, false]
-
A.
hasApproximateLocation
Indicates that an entity is associated with a location that is known only imprecisely or within a general area rather than an exact position.
-
B.
locationWhenGiven
Indicates the place where an entity is located at the time it is given or transferred to another entity.
-
C.
basedOnRealLocation
Indicates that something is derived from, inspired by, or modeled after an actual geographic place in the real world.
-
D.
hasLocationComponent
Indicates that something includes, is associated with, or is composed of a specific location-related part or element.
-
E.
hasSatelliteLocation
Indicates that an entity has a secondary or remote location associated with it, such as a branch, satellite office, or auxiliary site.
- 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_69e245f6c2e881909a228fdcfeb7c7d3 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18e11e9dc819093c569f388ffd46b |
completed | April 29, 2026, 4:50 a.m. |
| PD | Predicate disambiguation | batch_69ef89f020588190b43393e048e7eda3 |
completed | April 27, 2026, 4:08 p.m. |
| PDg | Predicate description generation | batch_69ef9b7494f4819088ae59ea3d0ae8ab |
completed | April 27, 2026, 5:23 p.m. |
Created at: April 17, 2026, 3:59 p.m.