Triple
T3711049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | hitsumabushi |
E81410
|
entity |
| Predicate | firstStageDescription |
P50951
|
FINISHED |
| Object | eel and rice eaten plain |
—
|
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: eel and rice eaten plain | Statement: [hitsumabushi, firstStageDescription, eel and rice eaten plain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstStageDescription Context triple: [hitsumabushi, firstStageDescription, eel and rice eaten plain]
-
A.
firstStageType
Indicates that one entity is the type or category of the first stage or initial phase associated with another entity.
-
B.
firstStageName
Indicates that one entity is the initial or earliest stage name associated with another entity in a sequence or lifecycle.
-
C.
firstStageEngine
Indicates that an engine functions as the primary propulsion unit used in the first stage of a multi-stage launch vehicle or rocket.
-
D.
firstScoreDescription
Indicates the textual description associated with an entity’s first or initial score.
-
E.
firstStageReusability
Indicates whether the first stage of a launch vehicle is designed to be recovered and reused after flight.
- 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_69ad8b1a81588190b3f27a5483bb610e |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adc584b86c8190ba1a1073da440b07 |
completed | March 8, 2026, 6:52 p.m. |
| PD | Predicate disambiguation | batch_69adc041a8608190a2d543dab6d2ef6c |
completed | March 8, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69adc133ef50819094c2b971f31f1615 |
completed | March 8, 2026, 6:34 p.m. |
Created at: March 8, 2026, 3:33 p.m.