Triple
T30558839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 勝矢 |
E777776
|
entity |
| Predicate | meaningComponent矢 |
P172526
|
FINISHED |
| Object | arrow |
—
|
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: arrow | Statement: [勝矢, meaningComponent矢, arrow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meaningComponent矢 Context triple: [勝矢, meaningComponent矢, arrow]
-
A.
meaningComponent郎
Indicates that one entity is a semantic component or constituent part of the overall meaning of another entity.
-
B.
meaningComponent
Indicates that one entity represents a semantic or conceptual component contributing to the overall meaning of another entity.
-
C.
meaningComponent新
Indicates that one entity represents a newly introduced or distinct component of the overall meaning or semantic structure of another entity.
-
D.
meaningComponent忠
Indicates that one entity is a loyal or faithful component, aspect, or part within the overall meaning or semantic structure of another entity.
-
E.
meaningComponent樹
Indicates that one entity represents a semantic or conceptual component contributing to the overall meaning of another entity.
- 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_69f2249ed41c8190b175170ecfd6e1c5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6ac1ed23c8190ace57ffc9d8a3dc6 |
completed | May 3, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69f6aba8fba48190bc1a17117244cae1 |
completed | May 3, 2026, 1:58 a.m. |
Created at: April 29, 2026, 8:21 p.m.