Triple
T11710245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Register of Cultural Heritage Monuments of Georgia |
E278354
|
entity |
| Predicate | dataContained |
P86949
|
FINISHED |
| Object | location of monuments |
—
|
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: location of monuments | Statement: [National Register of Cultural Heritage Monuments of Georgia, dataContained, location of monuments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataContained Context triple: [National Register of Cultural Heritage Monuments of Georgia, dataContained, location of monuments]
-
A.
containsDataAbout
chosen
Indicates that one entity holds or includes information or records pertaining to another entity.
-
B.
dataReturned
Indicates that some data has been sent back or provided as a result of a request, query, or operation.
-
C.
data
Indicates that one entity serves as informational content, measurements, or recorded values associated with another entity.
-
D.
dataHidden
Indicates that certain data is concealed, inaccessible, or not visible to users or systems under normal conditions.
-
E.
typicallyContain
Indicates that one entity is normally or commonly found within, included in, or held by another entity under usual circumstances.
- 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_69d6aaff2ce88190b4a1e4b341ad5377 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a49f072c81909c6a964a92e5bc0c |
completed | April 10, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69d88a7d483081909c2a101087515d74 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.