Triple
T4370693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carrick |
E98887
|
entity |
| Predicate | hasHistoricIdentityAs |
P6594
|
FINISHED |
| Object | Gaelic-speaking lordship |
—
|
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: Gaelic-speaking lordship | Statement: [Carrick, hasHistoricIdentityAs, Gaelic-speaking lordship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricIdentityAs Context triple: [Carrick, hasHistoricIdentityAs, Gaelic-speaking lordship]
-
A.
hasIdentity
chosen
Indicates that one entity is the same as, or is identified as, another specific entity or identifier.
-
B.
hasHistoricalEntity
Indicates a relationship where one entity includes, references, or is associated with another entity that existed or is defined in a past historical context.
-
C.
hasHistorySince
Indicates that an entity has maintained a particular state, condition, or relationship continuously starting from a specified point in time.
-
D.
hasHistoricalRoleAs
Indicates that an entity has served in a specific historical capacity, function, or position during a particular period or context.
-
E.
hasHistoricalProcess
Indicates that an entity is associated with, or characterized by, a historical process or sequence of events that unfolded over time.
- 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_69b3454db3708190aeafd814413c4c3d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3521cb7ec8190b7b79675871d97d8 |
completed | March 12, 2026, 11:54 p.m. |
| PD | Predicate disambiguation | batch_69b34f53e3cc8190bf5d4dbe2413bf65 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:17 p.m.