Triple
T19868653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Monuments Authority |
E477454
|
entity |
| Predicate | typeOfMonumentCovered |
P25584
|
FINISHED |
| Object | ancient 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: ancient monuments | Statement: [National Monuments Authority, typeOfMonumentCovered, ancient monuments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfMonumentCovered Context triple: [National Monuments Authority, typeOfMonumentCovered, ancient monuments]
-
A.
monumentType
chosen
Indicates the specific kind or category of monument that an entity is classified as.
-
B.
builtMonument
Indicates that one entity constructed or created a monument in honor of, or related to, another entity.
-
C.
eraOfOriginalMonuments
Indicates the historical time period during which the original monuments were created or first established.
-
D.
monumentSubject
Indicates that the subject serves as the monument or commemorative structure associated with another entity.
-
E.
hasNumberOfMonuments
Indicates the specific count of monuments associated with or present in a given 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_69d8e51e7d948190aedbcd6c30361c39 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e658a168288190a2fbb735d1fd30a8 |
completed | April 20, 2026, 4:47 p.m. |
| PD | Predicate disambiguation | batch_69e537e8c4e481909fe95d795b4864e7 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:51 p.m.