Triple
T11080950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clan Fraser |
E261988
|
entity |
| Predicate | earlyPresence |
P97108
|
FINISHED |
| Object | recorded in Scotland by the 12th 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: recorded in Scotland by the 12th century | Statement: [Clan Fraser, earlyPresence, recorded in Scotland by the 12th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earlyPresence Context triple: [Clan Fraser, earlyPresence, recorded in Scotland by the 12th century]
-
A.
modernPresence
Indicates that something exists, appears, or is active in the contemporary or present-day context.
-
B.
confirmedPresenceOf
Indicates that the presence or existence of an entity has been verified as true or established with certainty.
-
C.
globalPresence
Indicates that an entity operates, is represented, or has a significant footprint across multiple countries or world regions.
-
D.
typeOfPresence
Indicates the manner or mode in which an entity is present or exists in relation to another entity, context, or environment.
-
E.
hasHumanPresence
Indicates that humans are physically present in or occupying a given location, object, or context.
- 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_69d6aa9983c08190b0ef61603b69feac |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79996d9408190b159d14b23c25ed1 |
completed | April 9, 2026, 12:20 p.m. |
| PD | Predicate disambiguation | batch_69d74415403c81909778bcd829e8832e |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750ca52ec8190a559432a5de106fd |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:27 p.m.