Triple
T34709162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1st Viscount Astor |
E1000588
|
entity |
| Predicate | createdViscountcy |
P78853
|
FINISHED |
| Object | 1917 |
—
|
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: 1917 | Statement: [1st Viscount Astor, createdViscountcy, 1917]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdViscountcy Context triple: [1st Viscount Astor, createdViscountcy, 1917]
-
A.
createdViscount
chosen
Indicates that one entity granted or established the noble title of viscount for another entity.
-
B.
createdViscountIn
Indicates that an entity conferred or established the noble title of viscount in a particular place, context, or jurisdiction.
-
C.
hasNotableViscountcy
Indicates that an entity holds or is associated with a viscountcy that is considered notable or significant.
-
D.
succeededToViscountcyInYear
Indicates that one entity assumed or inherited the title of viscount in a specified year, succeeding the previous holder of that viscountcy.
-
E.
createdMarquess
Indicates that one entity formally established or granted the noble title of marquess to another entity.
- 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_69f76dab937881909c86f1b9ad50445f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69ff5803c02c81908b63067119f5e684 |
completed | May 9, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69ff576d8b308190b49a1e072a0ae661 |
completed | May 9, 2026, 3:49 p.m. |
Created at: May 3, 2026, 3:59 p.m.