Triple
T28386832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HIV-1 |
E719039
|
entity |
| Predicate | firstRecognized |
P4732
|
FINISHED |
| Object | early 1980s |
—
|
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: early 1980s | Statement: [HIV-1, firstRecognized, early 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstRecognized Context triple: [HIV-1, firstRecognized, early 1980s]
-
A.
recognizedFirstBy
chosen
Indicates that one entity was the earliest or initial recognizer, identifier, or acknowledger of another entity.
-
B.
primaryRecognition
Indicates that one entity is the main or foremost source of acknowledgment, credit, or validation for another entity.
-
C.
laterRecognizes
Indicates that one entity comes to acknowledge, identify, or realize something about another entity or situation at a subsequent point in time.
-
D.
resultRecognizedBy
Indicates that a particular result is formally acknowledged, validated, or accepted by a specified recognizing entity.
-
E.
earlyRecognition
Indicates that one entity recognizes, identifies, or acknowledges another entity or condition sooner than is typical or expected.
- 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_69eff6ef211081909d31d9be5f5567e6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_6a00037bf4148190a58593d30efdd3f8 |
completed | May 10, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_6a0000b7af608190b718fc4111bcdad8 |
completed | May 10, 2026, 3:51 a.m. |
Created at: April 28, 2026, 1:10 a.m.