Triple
T31357773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L II |
E799781
|
entity |
| Predicate | successorMonogram |
P198626
|
FINISHED |
| Object | A I |
—
|
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: A I | Statement: [L II, successorMonogram, A I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorMonogram Context triple: [L II, successorMonogram, A I]
-
A.
predecessorMonogram
Indicates that one monogram directly precedes another in a defined sequence or order.
-
B.
successorNamesake
Indicates that one entity is named after another entity that precedes it, typically as its successor or continuation in name.
-
C.
successorMonument
Indicates that one monument replaces, follows, or is designated as the subsequent monument to another in a sequence or historical succession.
-
D.
successorBranding
Indicates that one brand has replaced or continued another brand as its subsequent or updated identity.
-
E.
nicknameOfSuccessor
Indicates that one entity is a nickname or informal name used to refer to another entity that is its successor.
- 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_69f224e5e9bc8190a16339328897c4f8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fef8c3f2388190b995ec173512945a |
completed | May 9, 2026, 9:05 a.m. |
| PD | Predicate disambiguation | batch_69fef65975608190960b78d27e806d4f |
completed | May 9, 2026, 8:54 a.m. |
| PDg | Predicate description generation | batch_69fef8c2cdd881908c6f44e4dfa5ffd0 |
completed | May 9, 2026, 9:05 a.m. |
Created at: April 29, 2026, 9:17 p.m.