Triple
T19347352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hiroshi |
E483914
|
entity |
| Predicate | semanticVariability |
P13845
|
FINISHED |
| Object | meaning depends on kanji used |
—
|
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: meaning depends on kanji used | Statement: [Hiroshi, semanticVariability, meaning depends on kanji used]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: semanticVariability Context triple: [Hiroshi, semanticVariability, meaning depends on kanji used]
-
A.
variant
Indicates that one entity is an alternative form, version, or variation of another entity.
-
B.
hasVariability
chosen
Indicates that an entity exhibits variation or fluctuation in its state, value, or characteristics over time or across instances.
-
C.
arity
Indicates the number of arguments or participants that a relation or function takes.
-
D.
hasDirectionVariability
Indicates that the direction associated with an entity or process is not fixed but varies over time, space, or conditions.
-
E.
usesVAR
Indicates that one entity makes use of, employs, or utilizes another entity as a variable or resource in performing some function or operation.
- 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_69d8e8d244f8819080eb1f3491300db2 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e6185c95248190b1e5bb8626489767 |
completed | April 20, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69e4dd12303c8190a2027c062b2dff40 |
completed | April 19, 2026, 1:48 p.m. |
Created at: April 10, 2026, 1:34 p.m.