Triple
T35788755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Hidden Words |
E1034630
|
entity |
| Predicate | containsPassagesAddressedTo |
P158612
|
FINISHED |
| Object | children of men |
—
|
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: children of men | Statement: [The Hidden Words, containsPassagesAddressedTo, children of men]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsPassagesAddressedTo Context triple: [The Hidden Words, containsPassagesAddressedTo, children of men]
-
A.
storyAddressedTo
Indicates that a story is specifically directed or intended for a particular recipient or audience.
-
B.
isAddressedIn
chosen
Indicates that a particular topic, issue, or entity is discussed, handled, or dealt with within a specified document, communication, or context.
-
C.
isAddressedTo
Indicates that a message, communication, or item is specifically directed or intended for a particular recipient.
-
D.
addressedBy
Indicates that something (such as an issue, request, or item) is handled, dealt with, or responded to by a particular agent or entity.
-
E.
characterAddressed
Indicates that one character directs speech, communication, or attention specifically toward another character.
- 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_69f76e1575908190aaa306d843b41c14 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a00ccadb6908190ab810a7c05315fa8 |
completed | May 10, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_6a00cc0f86b88190a0d2c43618558f86 |
completed | May 10, 2026, 6:18 p.m. |
Created at: May 3, 2026, 4:06 p.m.