Triple
T33134529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moel Arthur |
E847964
|
entity |
| Predicate | hasGeologicalEra |
P165420
|
FINISHED |
| Object | Iron Age |
—
|
NE NERFINISHED |
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: Iron Age | Statement: [Moel Arthur, hasGeologicalEra, Iron Age]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGeologicalEra Context triple: [Moel Arthur, hasGeologicalEra, Iron Age]
-
A.
hasGeologicalHistory
Indicates that an entity possesses or is associated with a record or sequence of past geological events, formations, or processes.
-
B.
geologicalPeriodRelevance
chosen
Indicates that something is relevant to, associated with, or characteristic of a particular geological period.
-
C.
geologicalAge
Indicates the time period in Earth's geological history during which an entity (such as a rock, fossil, or formation) originated or was formed.
-
D.
studiedGeologicalPeriod
Indicates that an entity has conducted study or research focused on a particular geological period.
-
E.
brokeUpDuringGeologicEra
Indicates that a previously unified landmass or geological entity separated into distinct parts during a specified geologic era.
- 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_69f3495961d88190b16ea542c2c5f825 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
Created at: May 1, 2026, 1:27 a.m.