Triple
T10768038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drumcliff, County Sligo |
E254002
|
entity |
| Predicate | hasHighCrossFrom |
P30330
|
FINISHED |
| Object | 9th century |
—
|
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: 9th century | Statement: [Drumcliff, County Sligo, hasHighCrossFrom, 9th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighCrossFrom Context triple: [Drumcliff, County Sligo, hasHighCrossFrom, 9th century]
-
A.
hasCross
chosen
Indicates that one entity possesses, displays, or is marked by a cross in relation to another entity or context.
-
B.
hasHigh
Indicates that an entity possesses a high level, degree, or intensity of a specified attribute or property.
-
C.
hasMajorCrossing
Indicates that one entity has a significant or primary intersection or crossing with another entity.
-
D.
hasCrossunders
Indicates that one entity passes beneath or under another entity, forming a crossing relationship where it goes below rather than above.
-
E.
crossedBy
Indicates that one entity (typically a path, line, or boundary) is intersected or traversed by another entity.
- 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_69d6aa5f54f4819082d0bbcb6f8797e6 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d7322eb2f08190999e09428e7f7ba8 |
completed | April 9, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69d6f311529c819080ca5493d55d6050 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:16 p.m.