Triple
T11252145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juli Kidman |
E266343
|
entity |
| Predicate | loyaltyStatus |
P56014
|
FINISHED |
| Object | initially loyal to Mobius |
—
|
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: initially loyal to Mobius | Statement: [Juli Kidman, loyaltyStatus, initially loyal to Mobius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loyaltyStatus Context triple: [Juli Kidman, loyaltyStatus, initially loyal to Mobius]
-
A.
petitionerLoyaltyStatus
chosen
Indicates the current or historical loyalty or allegiance status of the petitioner in relation to a relevant authority, group, or cause.
-
B.
associatedLoyaltyStatus
Indicates that there is a connection between an entity and a specific loyalty status within a loyalty or rewards program.
-
C.
loyaltySymbolizedBy
Indicates that an instance of loyalty is represented or expressed by a particular symbol or emblem.
-
D.
loyaltyProgramTierOf
Indicates the specific loyalty or rewards program tier that an entity (such as a customer or account) belongs to.
-
E.
loyaltyProgramAccess
Indicates that an entity is granted rights or eligibility to participate in a specific loyalty or rewards program.
- 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_69d6aac7953c8190b82caf9d7640fdf9 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e933648481909873094bc89ed041 |
completed | April 9, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69d78793c00481908a3f764b610b77a4 |
completed | April 9, 2026, 11:03 a.m. |
Created at: April 8, 2026, 9:31 p.m.