Triple
T20083037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eglon |
E500049
|
entity |
| Predicate | receivesMessageDescribedAs |
P138650
|
FINISHED |
| Object | secret message from God |
—
|
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: secret message from God | Statement: [Eglon, receivesMessageDescribedAs, secret message from God]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivesMessageDescribedAs Context triple: [Eglon, receivesMessageDescribedAs, secret message from God]
-
A.
receives
Indicates that one entity is the recipient of something (such as an object, message, or action) from another entity.
-
B.
intendedMessage
Indicates that one entity is the message or content that another entity aims or plans to communicate.
-
C.
receivingState
Indicates that one entity serves as the recipient or destination of something (such as an object, message, or person) from another entity.
-
D.
messageHandling
Indicates how messages are received, processed, and responded to within a communication or messaging system.
-
E.
textReception
Indicates that an entity receives, reads, or otherwise takes in a piece of text produced or sent by another entity.
- 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_69da627770948190997f486f9a2e370f |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6655946f48190a6b4cb13ea4e212a |
completed | April 20, 2026, 5:41 p.m. |
| PD | Predicate disambiguation | batch_69e54cf369b88190931532420517dac7 |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc20888819083c9118a09d0d2dc |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 3:41 p.m.