Triple
T37408552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AS565 UB |
E929198
|
entity |
| Predicate | hasVariantRoleDifferenceFrom |
P56783
|
FINISHED |
| Object | AS565 MB |
—
|
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: AS565 MB | Statement: [AS565 UB, hasVariantRoleDifferenceFrom, AS565 MB]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVariantRoleDifferenceFrom Context triple: [AS565 UB, hasVariantRoleDifferenceFrom, AS565 MB]
-
A.
hasVariantRole
Indicates that an entity participates in a context or process while assuming an alternative or modified role compared to its primary or canonical role.
-
B.
hasVariant
Indicates that one entity exists as an alternative form, version, or variation of another entity.
-
C.
laterVariantRole
chosen
Indicates that one role is a subsequent or later variant of another, reflecting a modified or evolved version of the original role.
-
D.
hasVariantsIn
Indicates that an entity exists in multiple alternative forms or versions within a specified context or set.
-
E.
hasVariantSystem
Indicates that one system is an alternative or variant form of another system within the same general framework or category.
- 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_69f76ebbf79c8190b85bbcf3a6be57e4 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:16 p.m.