Triple
T14101168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monterozzi Necropolis |
E339382
|
entity |
| Predicate | numberOfPaintedTombs |
P112818
|
FINISHED |
| Object | over 200 |
—
|
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 200 | Statement: [Monterozzi Necropolis, numberOfPaintedTombs, over 200]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfPaintedTombs Context triple: [Monterozzi Necropolis, numberOfPaintedTombs, over 200]
-
A.
hasTombs
Indicates that one entity possesses, contains, or is the location of one or more tombs associated with another entity.
-
B.
hasApproximateNumberOfTombs
Indicates that an entity is associated with a tomb count that is approximate rather than exact.
-
C.
numberOfCoffins
Indicates the quantity of coffins associated with a given entity or situation.
-
D.
numberOfBurials
Indicates the total count of burial events associated with a given entity.
-
E.
tombNumber
Indicates the specific identifying number assigned to a particular tomb within a set of tombs.
- F. None of above. chosen
Provenance (4 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_69d81c69b5c8819094aa1abf18302908 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5fbbf0b08190ba1ea3657d6db005 |
completed | April 14, 2026, 3:39 p.m. |
| PD | Predicate disambiguation | batch_69de05b2f7e481908a9a7d40153234c0 |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de2398856c81908bed6070e4ca6ab1 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:22 p.m.