Triple
T22729598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trophonius |
E562094
|
entity |
| Predicate | afterEffectOnConsultants |
P149498
|
FINISHED |
| Object | lasting terror |
—
|
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: lasting terror | Statement: [Trophonius, afterEffectOnConsultants, lasting terror]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: afterEffectOnConsultants Context triple: [Trophonius, afterEffectOnConsultants, lasting terror]
-
A.
hasConsultants
Indicates that one entity engages or employs another entity to provide professional consulting services.
-
B.
consultsOn
Indicates that one entity provides expert advice, guidance, or professional input to another entity regarding a specific subject, project, or decision.
-
C.
worksAsConsultantFor
Indicates that one entity provides professional consulting services to another entity, typically on a contractual or advisory basis.
-
D.
consulted
Indicates that one entity sought advice, information, or guidance from another entity.
-
E.
appointedInConsultationWith
Indicates that an entity is appointed to a role or position through a process of consultation with another specified party or parties.
- F. None of above. chosen
Provenance (4 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_69e24550859c81908727d91efc3a81b4 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1792be7d88190b6d7d79041fcba25 |
completed | April 29, 2026, 3:21 a.m. |
| PD | Predicate disambiguation | batch_69eed2a971c0819088af574e40c9343f |
completed | April 27, 2026, 3:06 a.m. |
| PDg | Predicate description generation | batch_69eeeb5681f88190821129ced752f190 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:21 p.m.