Triple
T29017362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nildoror |
E737351
|
entity |
| Predicate | actuallyCharacterizedAs |
P662
|
FINISHED |
| Object | spiritually advanced |
—
|
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: spiritually advanced | Statement: [Nildoror, actuallyCharacterizedAs, spiritually advanced]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: actuallyCharacterizedAs Context triple: [Nildoror, actuallyCharacterizedAs, spiritually advanced]
-
A.
characterizedBy
chosen
Indicates that one entity possesses a defining quality, feature, or attribute expressed by another entity.
-
B.
stanceCharacterization
Indicates how an entity’s attitude, position, or viewpoint toward another entity, claim, or issue is characterized.
-
C.
usedForCharacterizationOf
Indicates that something is employed to describe, distinguish, or determine the characteristics or identity of another entity.
-
D.
relationshipCharacterizedAs
Indicates that one relationship is described, defined, or typified in terms of another specified characteristic or relational type.
-
E.
resultCharacterization
Indicates how the outcome of an event, process, or action is qualitatively described or characterized.
- 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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f65fe190a081909dabf1e185d1575a |
completed | May 2, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 9:46 a.m.