Triple
T37416339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Ross |
E929720
|
entity |
| Predicate | firstKnownEarlFlourished |
P205891
|
FINISHED |
| Object | early 13th 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: early 13th century | Statement: [Earl of Ross, firstKnownEarlFlourished, early 13th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstKnownEarlFlourished Context triple: [Earl of Ross, firstKnownEarlFlourished, early 13th century]
-
A.
yearOfCreationOfEarldom
Indicates the specific year in which a particular earldom was formally created or established.
-
B.
flourishedBefore
Indicates that one entity reached its peak or period of greatest development earlier in time than another entity.
-
C.
firstKnownLord
Indicates that the subject is the earliest historically or canonically recorded lord associated with the object.
-
D.
holdsOneOfOldestEarldomsIn
Indicates that an entity possesses one of the most ancient or historically earliest-established earldoms within a specified region or jurisdiction.
-
E.
flourishedAfter
Indicates that one entity reached its peak or period of prosperity subsequent to the flourishing or peak period of another entity.
- 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_69f76ebde49481908566cd96b37ccc84 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:16 p.m.