Triple
T21086542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tambora language |
E519502
|
entity |
| Predicate | classificationComment |
P65860
|
FINISHED |
| Object | not Austronesian |
—
|
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: not Austronesian | Statement: [Tambora language, classificationComment, not Austronesian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: classificationComment Context triple: [Tambora language, classificationComment, not Austronesian]
-
A.
classificationAccordingTo
Indicates that an entity is assigned a particular class, type, or category as defined or determined by a specified source, standard, or authority.
-
B.
classificationNote
chosen
Indicates a note or comment providing additional information or clarification about how something has been classified.
-
C.
classificationRole
Indicates that one entity serves as a classificatory role or type used to categorize or group another entity.
-
D.
classificationStart
Indicates the point in time or process at which a classification or categorization of an entity begins.
-
E.
classificationConsensus
Indicates that multiple agents or sources agree on the same classification or category assignment for a given entity or item.
- 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_69e0b507dd9081908fb8bfcbef4c8b46 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7094ad1c08190a4b9d2668a6362b2 |
completed | April 21, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69e5dbfcd5e881908f1e4e0d2d237856 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:50 p.m.