Triple
T15817439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Varyag |
E383514
|
entity |
| Predicate | roleInJapaneseService |
P120187
|
FINISHED |
| Object | training ship |
—
|
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: training ship | Statement: [Varyag, roleInJapaneseService, training ship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInJapaneseService Context triple: [Varyag, roleInJapaneseService, training ship]
-
A.
roleInShinKokinWakashu
Indicates the specific role or involvement an entity has in relation to the Shin Kokin Wakashū (e.g., as compiler, editor, or contributor).
-
B.
roleInGemini10
Indicates that an entity holds a specific role or position in the context of the Gemini 10 mission or project.
-
C.
roleInGemini3
Indicates that an entity holds a specific role or function within the Gemini 3 mission or project.
-
D.
roleInPhilippines
Indicates that an entity holds or has held an official or notable role, position, or function within the Philippines.
-
E.
roleInBabel
Indicates that an entity participates in the Babel project or system with a specific role or function.
- 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_69d86da2858c819090cc8481e7207b6e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0c4a4332c8190bc525e06d6f3a6b4 |
completed | April 16, 2026, 11:14 a.m. |
| PD | Predicate disambiguation | batch_69e0053b847c8190945726c3ddac21cc |
completed | April 15, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69e00e48d49c819081afccb02f9cf18b |
completed | April 15, 2026, 10:16 p.m. |
Created at: April 10, 2026, 4:49 a.m.