Triple
T34109980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pagan Archaeological Zone |
E874811
|
entity |
| Predicate | originalNumberOfMonuments |
P32446
|
FINISHED |
| Object | over 10000 monuments at its height |
—
|
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 10000 monuments at its height | Statement: [Pagan Archaeological Zone, originalNumberOfMonuments, over 10000 monuments at its height]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalNumberOfMonuments Context triple: [Pagan Archaeological Zone, originalNumberOfMonuments, over 10000 monuments at its height]
-
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.
originalMonumentsFrom
Indicates that certain monuments were originally created, erected, or located in a specified place or source region.
-
D.
spawnsCountPerMonument
Indicates the number of spawn events or instances associated with each individual monument.
-
E.
eraOfOriginalMonuments
Indicates the historical time period during which the original monuments were created or first established.
- 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_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:53 a.m.