Triple
T20360575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scarus |
E496764
|
entity |
| Predicate | hasLoyaltyTrait |
P94124
|
FINISHED |
| Object | loyal follower of Mark Antony |
—
|
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: loyal follower of Mark Antony | Statement: [Scarus, hasLoyaltyTrait, loyal follower of Mark Antony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLoyaltyTrait Context triple: [Scarus, hasLoyaltyTrait, loyal follower of Mark Antony]
-
A.
hasLoyalties
Indicates that an entity feels allegiance or commitment toward one or more other entities or causes.
-
B.
loyaltySymbolizedBy
Indicates that an instance of loyalty is represented or expressed by a particular symbol or emblem.
-
C.
isLoyalTo
chosen
Indicates that one entity consistently supports, respects, or remains faithful to another entity.
-
D.
loyaltyProgramAccess
Indicates that an entity is granted rights or eligibility to participate in a specific loyalty or rewards program.
-
E.
petitionerLoyaltyStatus
Indicates the current or historical loyalty or allegiance status of the petitioner in relation to a relevant authority, group, or cause.
- 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_69e0b4a3f7f48190b37f354574028ca6 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e678584294819093788ccf2fb8e588 |
completed | April 20, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69e57636b4808190bc2855af48a3ccdc |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:25 a.m.