Triple
T30120109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Havers |
E765536
|
entity |
| Predicate | notableTitleHolderField |
P207210
|
FINISHED |
| Object | law |
—
|
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: law | Statement: [Baron Havers, notableTitleHolderField, law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableTitleHolderField Context triple: [Baron Havers, notableTitleHolderField, law]
-
A.
titleHolderNotably
Indicates that an entity holds a particular title in a way that is especially notable, distinguished, or worthy of specific mention.
-
B.
notableTitleType
Indicates that a title associated with an entity is of a type considered notable or especially significant.
-
C.
hasTitleHolderNotability
Indicates that the title holder possesses a notable or distinguished level of recognition or significance.
-
D.
hasNotableTitleHolderWhoBecame
Indicates that an entity has a notable title holder who later attained or transitioned into another specified role, status, or position.
-
E.
notableTitleAssociation
Indicates an association where an entity is linked to a distinguished or noteworthy title, role, or honor it holds or has held.
- 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_69f2247716748190ae4f16998f49ddf1 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 29, 2026, 7:13 p.m.