Triple
T9272986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tara of the Kings |
E222874
|
entity |
| Predicate | hasEarthwork |
P24197
|
FINISHED |
| Object | ringforts |
—
|
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: ringforts | Statement: [Tara of the Kings, hasEarthwork, ringforts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEarthwork Context triple: [Tara of the Kings, hasEarthwork, ringforts]
-
A.
hasSoil
Indicates that one entity possesses, contains, or is associated with a particular type or instance of soil.
-
B.
hasArchaeologicalMound
chosen
Indicates that an entity possesses or contains an archaeological mound, i.e., a raised earthwork or mound of archaeological significance located on or within it.
-
C.
hasLandReclamation
Indicates that an entity has carried out, is involved in, or is characterized by the process of creating new land from oceans, rivers, or other water bodies.
-
D.
hasLandform
Indicates that one entity possesses, contains, or is characterized by a particular natural landform.
-
E.
hasGeologicalSignificance
Indicates that something possesses notable importance or relevance within a geological context, such as Earth’s structure, history, or processes.
- 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_69ca841ffe208190aa7bcffbef2f8379 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd0787d2e48190ad56cf3abf12d409 |
completed | April 1, 2026, 11:54 a.m. |
| PD | Predicate disambiguation | batch_69cc7a537bbc8190baee71f556e52a7b |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:33 p.m.