Triple
T34237018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lion XI |
E878363
|
entity |
| Predicate | relativeToOtherVariants |
P154137
|
FINISHED |
| Object | later variant |
—
|
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: later variant | Statement: [Lion XI, relativeToOtherVariants, later variant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeToOtherVariants Context triple: [Lion XI, relativeToOtherVariants, later variant]
-
A.
exportVariantOf
Indicates that one entity is an exported version or externally released form derived from another, original entity.
-
B.
rulesVariantOf
Indicates that one set of rules is a modified or alternative version derived from another set of rules.
-
C.
denotesVariantOf
chosen
Indicates that one entity is a variant or alternative form of another, typically sharing core identity or function with some differences.
-
D.
relatedSpeciesOrVariant
Indicates that one species or biological variant is taxonomically or genetically related to another.
-
E.
likelyVariantOf
Indicates that one entity is probably a variant, version, or alternative form of another entity, based on available evidence or similarity.
- 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_69f349b22d8c819096b22df268382aa9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:56 a.m.