Triple
T30430691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viscount Fauconberg |
E774154
|
entity |
| Predicate | subsequentCreation |
P170221
|
FINISHED |
| Object | Earldom of Fauconberg |
—
|
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 Fauconberg | Statement: [Viscount Fauconberg, subsequentCreation, Earldom of Fauconberg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subsequentCreation Context triple: [Viscount Fauconberg, subsequentCreation, Earldom of Fauconberg]
-
A.
subsequentUse
Indicates that one entity is used, applied, or consumed after another entity in time or sequence.
-
B.
subsequentCase
Indicates that one legal case follows another in time or procedural order, often relying on or referencing the earlier case.
-
C.
subsequentPublication
Indicates that one publication was released after another in time, making it a later or follow-up work relative to the first.
-
D.
secondCreationStatus
Indicates the status or outcome of a second or subsequent creation event associated with an entity.
-
E.
subsequentIncrease
Indicates that one quantity or value increases after a prior event, state, or change has occurred.
- 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_69f22492d2a88190995ce8745d9becaa |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68b121eac81909e90416207bc1157 |
completed | May 2, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f68a160374819084d720985f800dfc |
completed | May 2, 2026, 11:34 p.m. |
Created at: April 29, 2026, 8:06 p.m.