Triple
T9777855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Servant of the Secret Fire |
E237290
|
entity |
| Predicate | signifiesRoleAs |
P57555
|
FINISHED |
| Object | divine emissary |
—
|
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: divine emissary | Statement: [Servant of the Secret Fire, signifiesRoleAs, divine emissary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signifiesRoleAs Context triple: [Servant of the Secret Fire, signifiesRoleAs, divine emissary]
-
A.
reflectsRoleAs
chosen
Indicates that one entity expresses, represents, or makes evident the role, function, or position held by another entity.
-
B.
acknowledgesRoleOf
Indicates that one entity explicitly recognizes and accepts the position, function, or authority that another entity holds.
-
C.
definesRole
Indicates that one entity specifies or establishes the role, function, or position of another entity within a given context.
-
D.
servesRole
Indicates that one entity performs, fulfills, or occupies a particular function, position, or responsibility in relation to another entity.
-
E.
identificationRole
Indicates that an entity serves as an identifier or plays a role in uniquely distinguishing or recognizing 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_69ca84d975a08190aab25b02a89bdab3 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda13545808190a47544b0cc666e20 |
completed | April 1, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69cd03d77c6c81909b675955bf113320 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:26 p.m.