Triple
T919963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LPC |
E19859
|
entity |
| Predicate | typeOfDesignation |
P19278
|
FINISHED |
| Object | individual landmark designation |
—
|
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: individual landmark designation | Statement: [LPC, typeOfDesignation, individual landmark designation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfDesignation Context triple: [LPC, typeOfDesignation, individual landmark designation]
-
A.
designatorType
Indicates the specific role or category of a designator used to identify or reference an entity within a system or context.
-
B.
designationType
chosen
Indicates the specific category or kind of formal status, title, or label that has been assigned in a designation relationship.
-
C.
hasDesignation
Indicates that an entity holds or is assigned a specific title, label, or formal designation.
-
D.
mapDesignation
Indicates a formal label or identifier that is assigned to something specifically for use on a map.
-
E.
NATODesignation
Indicates that one entity is the official name or code assigned to another entity by NATO for identification or classification purposes.
- 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_69a493a099788190a696d9d8408cbaf4 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b388f0bc8190a087222636135ba5 |
completed | March 1, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69a4b2944ff88190a260be5355132ba5 |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.