Triple
T12801669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nozomi |
E306032
|
entity |
| Predicate | classAvailable |
P95791
|
FINISHED |
| Object | Ordinary Class |
—
|
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: Ordinary Class | Statement: [Nozomi, classAvailable, Ordinary Class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: classAvailable Context triple: [Nozomi, classAvailable, Ordinary Class]
-
A.
availableInClass
chosen
Indicates that something can be accessed, used, or is valid within the scope of a particular class.
-
B.
usesClass
Indicates that one entity makes use of, depends on, or is implemented using a particular class in its structure or behavior.
-
C.
classIntroduced
Indicates that a particular class (e.g., in a programming language or system) has been newly defined or made available within a given context or scope.
-
D.
supportedClass
Indicates that one entity is a class or type that is recognized, handled, or operable within the capabilities or context provided by another entity.
-
E.
configurationAvailable
Indicates that a specific configuration option or setup is present and can be used or applied in the given context.
- 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_69d7bdf366888190a8cccb982606889c |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e7d3f5c8190bf01bef5d263ca26 |
completed | April 10, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69d9640ed7448190b276e7fab649f7d2 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:30 p.m.