Triple
T32053438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rice family |
E818549
|
entity |
| Predicate | languageOfWorkDocument |
P134227
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [Rice family, languageOfWorkDocument, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfWorkDocument Context triple: [Rice family, languageOfWorkDocument, English]
-
A.
languageOfUnderlyingWork
Indicates the language in which the original or underlying work (from which a derived or related work stems) is expressed.
-
B.
languageOfDocumentation
Indicates the language in which the documentation for an entity is written or provided.
-
C.
languageOfWorkRecognized
Indicates that a work is officially recognized as being created or expressed in a particular language.
-
D.
languageSpecifies
Indicates that one entity defines or constrains the syntax, semantics, or usage rules that govern how another language or linguistic system is expressed or interpreted.
-
E.
languageOfManuscript
chosen
Indicates the language in which a given manuscript is written.
- 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_69f348fdacec8190b9f74375ca3b2094 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ffbe9e47688190a2692566dc326646 |
completed | May 9, 2026, 11:09 p.m. |
| PD | Predicate disambiguation | batch_69ffbb7b45388190b62cbde5c2d435cd |
completed | May 9, 2026, 10:55 p.m. |
Created at: May 1, 2026, 12:21 a.m.