Triple
T23815204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rathcroghan complex |
E589075
|
entity |
| Predicate | numberOfRecordedMonuments |
P32446
|
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: [Rathcroghan complex, numberOfRecordedMonuments, over 200]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfRecordedMonuments Context triple: [Rathcroghan complex, numberOfRecordedMonuments, over 200]
-
A.
hasNumberOfMonuments
chosen
Indicates the specific count of monuments associated with or present in a given entity.
-
B.
numberOfArchaeologicalSites
Indicates the total count of archaeological sites associated with a given entity or context.
-
C.
originalMonumentsFrom
Indicates that certain monuments were originally created, erected, or located in a specified place or source region.
-
D.
hasScheduledMonument
Indicates that an entity is associated with, or contains, a site or structure officially designated as a scheduled monument.
-
E.
numberOfIndividualGeoglyphsApprox
Indicates an approximate count of distinct individual geoglyphs associated with a given subject.
- 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_69e25d18619081909c7fb89d8926f14a |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c7aa91cc81909cc41db5c9c71fe5 |
completed | April 29, 2026, 8:56 a.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:58 p.m.