Triple
T38149302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weapon XVI |
E952706
|
entity |
| Predicate | loyaltyEnforcedTo |
P166292
|
FINISHED |
| Object | Weapon Plus objectives |
—
|
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: Weapon Plus objectives | Statement: [Weapon XVI, loyaltyEnforcedTo, Weapon Plus objectives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loyaltyEnforcedTo Context triple: [Weapon XVI, loyaltyEnforcedTo, Weapon Plus objectives]
-
A.
loyaltyRequirement
chosen
Indicates a condition specifying the level or type of loyalty that must be met for the relationship or action to hold.
-
B.
loyaltyAtStart
Indicates that a specified level or state of loyalty is present at the beginning of a defined period, event, or interaction.
-
C.
isLoyalTo
Indicates that one entity consistently supports, respects, or remains faithful to another entity.
-
D.
loyaltyRevealedIn
Indicates that an entity’s loyalty becomes evident or is demonstrated through a particular situation, action, or context.
-
E.
hasLoyalties
Indicates that an entity feels allegiance or commitment toward one or more other entities or causes.
- 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_69f76f0a67f4819080c492f61d688fcc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcb089a8f881909aa9e722babd43f7 |
completed | May 7, 2026, 3:32 p.m. |
| PD | Predicate disambiguation | batch_69fc45666c5c8190913bd632ac0e5b84 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:21 p.m.