Triple
T10774183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calleja’s reputation as a royalist commander increased |
E254155
|
entity |
| Predicate | hasPerceptionBy |
P4830
|
FINISHED |
| Object | royalist officers |
—
|
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: royalist officers | Statement: [Calleja’s reputation as a royalist commander increased, hasPerceptionBy, royalist officers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPerceptionBy Context triple: [Calleja’s reputation as a royalist commander increased, hasPerceptionBy, royalist officers]
-
A.
hasPerception
chosen
Indicates that one entity is aware of, senses, or recognizes another entity or phenomenon.
-
B.
hasFanPerception
Indicates that an entity is perceived, interpreted, or regarded in a particular way by its fans or fan community.
-
C.
perceptionBySelf
Indicates that an entity has a perception, awareness, or sensory experience of itself.
-
D.
hasSupernaturalPerceptionOf
Indicates that one entity possesses a supernatural or extrasensory awareness, insight, or perception specifically directed toward another entity.
-
E.
hasSee
Indicates that one entity has perceived or visually observed another entity.
- 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_69d6aa5f54f4819082d0bbcb6f8797e6 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d7329be784819083b7ec4d85c20acf |
completed | April 9, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69d6f31455648190b5c24690487b1b54 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:16 p.m.