Triple
T35013344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Falinesti |
E1009988
|
entity |
| Predicate | mapStatus |
P97480
|
FINISHED |
| Object | Exact current location unknown |
—
|
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: Exact current location unknown | Statement: [Falinesti, mapStatus, Exact current location unknown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mapStatus Context triple: [Falinesti, mapStatus, Exact current location unknown]
-
A.
mapDisplay
Indicates that something is being visually represented or shown on a map interface.
-
B.
mapState
Indicates a correspondence that associates each element of one set or context (the "state") with a specific element or configuration in another, effectively translating or transforming state information between them.
-
C.
mapUse
Indicates a relationship where one entity uses, applies, or employs a map (or mapping) to perform an action or achieve a purpose.
-
D.
mapVisibility
Indicates that one entity controls or reflects whether another entity is visible or hidden on a map.
-
E.
cartographyStatus
chosen
Indicates the current state or condition of mapping or map-making activities associated with an entity.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7858aa5508190a07dde993b3356fc |
completed | May 3, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.