Triple
T749940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl |
E15423
|
entity |
| Predicate | usedAsTitleInFull |
P18764
|
FINISHED |
| Object | Earl of [place or family name] |
—
|
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: Earl of [place or family name] | Statement: [Earl, usedAsTitleInFull, Earl of [place or family name]]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsTitleInFull Context triple: [Earl, usedAsTitleInFull, Earl of [place or family name]]
-
A.
usedAsTitleBeforeName
Indicates that a term or phrase functions as a formal title placed immediately before a person's name.
-
B.
usesTitle
Indicates that one entity refers to or addresses another entity using a specific title or formal designation.
-
C.
containsTitle
Indicates that one entity includes or holds another entity’s title as part of its content or metadata.
-
D.
uscTitle
Indicates that something is identified as a specific title within the United States Code (U.S.C.).
-
E.
hasTitleInLaw
Indicates that an entity holds or is designated by a specific formal title as defined or recognized in law.
- 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_69a493599a0081908da65f3407af1ef2 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a6304e0c8190827fb57c5cac2da9 |
completed | March 1, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69a4a5004f708190a984ee221716e19c |
completed | March 1, 2026, 8:43 p.m. |
| PDg | Predicate description generation | batch_69a4a58c0a84819094f07658dc651b36 |
completed | March 1, 2026, 8:46 p.m. |
Created at: March 1, 2026, 7:37 p.m.