Triple
T3859390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maiden Castle hillfort |
E90096
|
entity |
| Predicate | likelyDatingFrom |
P52397
|
FINISHED |
| Object | Iron Age |
—
|
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: Iron Age | Statement: [Maiden Castle hillfort, likelyDatingFrom, Iron Age]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: likelyDatingFrom Context triple: [Maiden Castle hillfort, likelyDatingFrom, Iron Age]
-
A.
likelyDatingTo
Indicates that something probably originates from or was created in a particular time period or date range.
-
B.
engagedTo
Indicates that two entities are formally committed to marry each other.
-
C.
loveInterest
Indicates that one entity is the romantic object of affection or attraction for another entity.
-
D.
possibleSocialStatus
Indicates that one entity may hold, attain, or be associated with a particular social status in relation to another context or system.
-
E.
hasSuitors
Indicates that an entity is the object of romantic or marital interest from one or more other entities.
- 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_69aed95b3c088190a8f85d19e6070599 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeec1ff39c8190b83a88abd840a0e3 |
completed | March 9, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69aee752c8a48190a670f73ed0bf1e61 |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aeeb828fb08190901d51edbe8bd304 |
completed | March 9, 2026, 3:47 p.m. |
Created at: March 9, 2026, 3:19 p.m.