Triple
T24267865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roberts |
E604891
|
entity |
| Predicate | nobleRankOfTitle |
P53396
|
FINISHED |
| Object | earl |
—
|
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 | Statement: [Roberts, nobleRankOfTitle, earl]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nobleRankOfTitle Context triple: [Roberts, nobleRankOfTitle, earl]
-
A.
nobleTitleOrStatus
Indicates that one entity holds, claims, or is associated with a particular noble rank, title, or social status in relation to another entity.
-
B.
nobleTitleElevated
Indicates that an entity’s noble rank or title has been raised to a higher level of nobility.
-
C.
nobleTitleNumber
Indicates the ordinal number or sequence position associated with a person's noble title (e.g., first duke, second baron).
-
D.
nobleTitleFrom
Indicates that a person derives or holds their noble title from a specified source, such as a place, lineage, or authority.
-
E.
nobleRankType
chosen
Indicates the specific category or level of nobility associated with an entity within a hierarchical noble rank system.
- 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_69e29544c29c8190b023606eafe5d36a |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28d55b4708190ad819403011cf64f |
completed | April 29, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69f1c450aa508190bc9d372a5f6ee47a |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:06 a.m.