Triple
T31959230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aplu |
E815988
|
entity |
| Predicate | possibleDomain |
P141997
|
FINISHED |
| Object | plague |
—
|
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: plague | Statement: [Aplu, possibleDomain, plague]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: possibleDomain Context triple: [Aplu, possibleDomain, plague]
-
A.
hasPossibleDomain
chosen
Indicates that a property or relation may apply to, or be defined over, a particular class or type of entities, without asserting that this is its only or actual domain.
-
B.
inputDomain
Indicates that a function, process, or system accepts inputs belonging to a specified domain or set of allowable values.
-
C.
typicalDomain
Indicates that one entity is the characteristic or most common domain, context, or area of application in which another entity typically occurs or is used.
-
D.
affectedDomain
Indicates the domain, field, or area that is impacted or influenced by a given action, event, or condition.
-
E.
possibleField
Indicates that an entity may be associated with, or located within, a particular field or domain, but this association is not certain or exclusive.
- 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_69f348f4ec708190abbb2a7c3ed58844 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 12:08 a.m.