Triple
T33660602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carington |
E862340
|
entity |
| Predicate | linkedNobleTitleSpelling |
P195553
|
FINISHED |
| Object | Carrington |
—
|
NE NERFINISHED |
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: Carrington | Statement: [Carington, linkedNobleTitleSpelling, Carrington]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedNobleTitleSpelling Context triple: [Carington, linkedNobleTitleSpelling, Carrington]
-
A.
associatedNobleTitle
Indicates that an entity is linked to or bears a particular noble or aristocratic title.
-
B.
nobleTitlePattern
Indicates a relationship where an entity’s noble title follows a specific structural or linguistic pattern.
-
C.
nobleTitleTo
Indicates that one entity holds or is assigned a specific noble title in relation to another entity (such as a person, territory, or institution).
-
D.
nobleTitleFrom
Indicates that a person derives or holds their noble title from a specified source, such as a place, lineage, or authority.
-
E.
nobilityTitleType
Indicates the specific kind or category of noble rank or title associated with an 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_69f34984c4008190bb82f33a7819da64 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fdd92396788190ae1424bc1ae55844 |
completed | May 8, 2026, 12:37 p.m. |
| PD | Predicate disambiguation | batch_69fdd678f40481909a717a2daec83b36 |
completed | May 8, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69fdd922d73c81908ad3faade247ec16 |
completed | May 8, 2026, 12:37 p.m. |
Created at: May 1, 2026, 1:42 a.m.