Triple
T4922192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Telephus |
E110490
|
entity |
| Predicate | exposedAsInfant |
P14188
|
FINISHED |
| Object | yes (in some versions) |
—
|
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: yes (in some versions) | Statement: [Telephus, exposedAsInfant, yes (in some versions)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exposedAsInfant Context triple: [Telephus, exposedAsInfant, yes (in some versions)]
-
A.
exposed
chosen
Indicates that one entity has been made visible, revealed, or left unprotected to another entity or to some external influence.
-
B.
exposedDuring
Indicates that something becomes visible, accessible, or subject to influence specifically within a given time period, event, or contextual interval.
-
C.
exposes
Indicates making something visible, known, or vulnerable by removing cover, concealment, or protection.
-
D.
birthType
Indicates the manner or method by which a birth occurred or was brought about.
-
E.
illegitimateChildOf
Indicates that one person is the child of another, but the parent–child relationship is not recognized as lawful or legitimate under the relevant social or legal norms.
- 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_69bd4413f9908190afcff44d7929cc4c |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ffc2ab08190992db2400562bcee |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3421588190ab08e92b9558042e |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:30 p.m.