Triple
T24573468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portroe |
E608027
|
entity |
| Predicate | hasViewpointNearby |
P127881
|
FINISHED |
| Object | Graves of the Leinstermen |
—
|
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: Graves of the Leinstermen | Statement: [Portroe, hasViewpointNearby, Graves of the Leinstermen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasViewpointNearby Context triple: [Portroe, hasViewpointNearby, Graves of the Leinstermen]
-
A.
hasViewingPointFor
Indicates that one entity serves as a vantage point or location from which another entity can be viewed or observed.
-
B.
viewpointNear
chosen
Indicates that one entity serves as a viewpoint or vantage location that is geographically close to another entity.
-
C.
hasNearbyMode
Indicates that one entity has another entity located close enough to be considered in its immediate vicinity or surrounding area.
-
D.
hasNotableNearbyEntity
Indicates that one entity has another significant or noteworthy entity located in its close physical or contextual proximity.
-
E.
hasViewpointStatus
Indicates that an entity holds a particular evaluative or perspectival status (e.g., stance, opinion, or viewpoint classification) with respect to something.
- 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_69e2c4cdab6c8190aae6e5d3de55c95e |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a9269360819090c44f4483c3533c |
completed | April 30, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69f2a6c1f07081908edf0b521767e79b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:28 a.m.