Triple
T19399048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silas |
E485267
|
entity |
| Predicate | returnsWhen |
P78008
|
FINISHED |
| Object | he is old and sick |
—
|
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: he is old and sick | Statement: [Silas, returnsWhen, he is old and sick]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnsWhen Context triple: [Silas, returnsWhen, he is old and sick]
-
A.
returns
Indicates that one entity gives or sends something back to another entity, often as a result or outcome of a process or action.
-
B.
returnsAs
Indicates that one entity goes back to or resumes a previous state, location, role, or condition associated with another entity.
-
C.
returnedDuring
Indicates that one entity was given back or restored to another entity within a specified time period or event.
-
D.
returnedWith
Indicates that an entity came back or was brought back accompanied by, or in possession of, another specified entity.
-
E.
returnCondition
chosen
Indicates the terms, state, or circumstances under which something that was previously given, lent, or transferred is expected or required to be returned.
- 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_69d8e8d5162481909db12435d9535c1a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e62575d78881909c2cfee799859261 |
completed | April 20, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69e4fd602f008190aa9bc76ae17e4ce1 |
completed | April 19, 2026, 4:05 p.m. |
Created at: April 10, 2026, 1:36 p.m.