Triple
T17262054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | congenital Zika syndrome |
E419030
|
entity |
| Predicate | firstRecognizedAround |
P123477
|
FINISHED |
| Object | 2015 |
—
|
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: 2015 | Statement: [congenital Zika syndrome, firstRecognizedAround, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstRecognizedAround Context triple: [congenital Zika syndrome, firstRecognizedAround, 2015]
-
A.
positionRecognized
Indicates that an entity’s role, status, or spatial position has been formally acknowledged or accepted by another entity or system.
-
B.
recognizableWhen
Indicates that one entity can be correctly identified or distinguished under the conditions, context, or representation specified by another entity.
-
C.
firstClearlyRecognizedIn
chosen
Indicates the point in time or context when something was first clearly identified, acknowledged, or distinguished as such.
-
D.
recognizedFirstBy
Indicates that one entity was the earliest or initial recognizer, identifier, or acknowledger of another entity.
-
E.
timePeriodRecognized
Indicates that a specific span of time has been formally identified or acknowledged as significant or valid within a given context.
- 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_69d886d9ab108190b70edd8d17aa1204 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42e717a348190ae6835fb08f38125 |
completed | April 19, 2026, 1:22 a.m. |
| PD | Predicate disambiguation | batch_69e3832a284481908a8a3da7ac91de5a |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:39 a.m.