Triple
T34109979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pagan Archaeological Zone |
E874811
|
entity |
| Predicate | estimatedNumberOfMonuments |
P32446
|
FINISHED |
| Object | over 2000 surviving 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: over 2000 surviving monuments | Statement: [Pagan Archaeological Zone, estimatedNumberOfMonuments, over 2000 surviving monuments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estimatedNumberOfMonuments Context triple: [Pagan Archaeological Zone, estimatedNumberOfMonuments, over 2000 surviving monuments]
-
A.
hasNumberOfMonuments
chosen
Indicates the specific count of monuments associated with or present in a given entity.
-
B.
isMonumentNumber
Indicates that one entity is the official monument identification number assigned to another entity.
-
C.
hasNumberOfMuseums
Indicates the quantity of museums associated with a given entity.
-
D.
monumentGroup
Indicates that one monument belongs to, or is categorized within, a specific group or collection of monuments.
-
E.
monumentState
Indicates that a monument is located within, or officially associated with, a particular state or state-level administrative region.
- 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_69f349a80d4481908527317d43f5c579 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: May 1, 2026, 1:53 a.m.