Triple
T33592592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arby |
E860468
|
entity |
| Predicate | hasUnsettlingDemeanor |
P86122
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Arby, hasUnsettlingDemeanor, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUnsettlingDemeanor Context triple: [Arby, hasUnsettlingDemeanor, true]
-
A.
hasVengefulTone
Indicates that the subject expresses anger, resentment, or a desire for revenge toward another entity in its tone or manner.
-
B.
becomesHostileWhen
Indicates that one entity starts to act with hostility toward another entity when a specified condition or trigger occurs.
-
C.
aggressiveness
Indicates a tendency or disposition of an entity to initiate hostile, forceful, or confrontational actions toward others.
-
D.
hasOppositionalPerception
Indicates that one entity perceives another entity, concept, or situation as being in opposition, conflict, or contradiction to itself or its interests.
-
E.
hasManner
chosen
Indicates the way, style, or method in which an action is performed or a relation is carried out.
- 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_69f3497e70e48190951c94d072879bec |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 1, 2026, 1:40 a.m.