Triple
T23814763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lennox family |
E589063
|
entity |
| Predicate | originatesFromTitle |
P87898
|
FINISHED |
| Object | Earldom of Lennox |
—
|
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: Earldom of Lennox | Statement: [Lennox family, originatesFromTitle, Earldom of Lennox]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originatesFromTitle Context triple: [Lennox family, originatesFromTitle, Earldom of Lennox]
-
A.
originallyTitleOf
Indicates that one title is the original title from which another work, edition, or localized title is derived.
-
B.
sourceOfTitle
Indicates that one entity is the origin or provider of another entity’s title or designation.
-
C.
usedTitleFrom
Indicates that one entity has employed or adopted the title originating from another entity.
-
D.
originatesAs
Indicates that one entity begins, arises, or comes into existence in the form, state, or role specified by another entity.
-
E.
notableTitleOrigin
chosen
Indicates that a notable or distinguished title held by an entity originates from, or is derived from, a specified source or context.
- 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_69e25d18619081909c7fb89d8926f14a |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c7a9ce708190a27195d58589d757 |
completed | April 29, 2026, 8:56 a.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:57 p.m.