Triple
T28073367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Levain |
E709467
|
entity |
| Predicate | packagingLanguage |
P164390
|
FINISHED |
| Object | Japanese |
—
|
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: Japanese | Statement: [Levain, packagingLanguage, Japanese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: packagingLanguage Context triple: [Levain, packagingLanguage, Japanese]
-
A.
packaging
Indicates that one entity serves as the container, wrapper, or enclosing material used to package another entity.
-
B.
languageOfImplementation
Indicates the programming language in which a given software system, component, or algorithm is implemented.
-
C.
languageOfPrimaryCompilation
Indicates the programming or source language in which an entity was primarily compiled.
-
D.
projectLanguageCode
Indicates the programming or markup language used in a project, represented by its standardized language code.
-
E.
packagingRequirement
Indicates the specific conditions, standards, or constraints that must be met in how something is packaged.
- F. None of above. chosen
Provenance (4 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_69ef9b6f8078819098b741274cd1a2ee |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f644de4a84819087ddb84757fc4585 |
completed | May 2, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69f641def1e88190a05bf865ced78b23 |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f643e818d481908fc66bc91bd25d77 |
completed | May 2, 2026, 6:35 p.m. |
Created at: April 27, 2026, 8:47 p.m.