Triple
T18428039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trauco |
E450189
|
entity |
| Predicate | explanationFor |
P3638
|
FINISHED |
| Object | unexplained pregnancies |
—
|
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: unexplained pregnancies | Statement: [Trauco, explanationFor, unexplained pregnancies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: explanationFor Context triple: [Trauco, explanationFor, unexplained pregnancies]
-
A.
usedToExplain
chosen
Indicates that one entity serves as an explanation or clarification for another entity.
-
B.
aimsToExplain
Indicates that one entity intends to clarify, make understandable, or provide an explanation about another entity, concept, or situation.
-
C.
laterExplained
Indicates that an earlier event, statement, or situation is clarified or made understandable by information provided at a subsequent time.
-
D.
hasOfficialExplanation
Indicates that an entity is accompanied by an authoritative or formally recognized explanation clarifying its reason, cause, or details.
-
E.
claimsToExplain
Indicates that one entity asserts it can provide a clarification, account, or understanding of another entity or phenomenon.
- 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_69d8d381d6388190a9e94e9c658174e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e51b14c4d481909af975575a43c4e1 |
completed | April 19, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69e469bf7f74819096a01173493412c2 |
completed | April 19, 2026, 5:35 a.m. |
Created at: April 10, 2026, 11:25 a.m.