Triple
T36916006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russo-Japanese War |
E913046
|
entity |
| Predicate | occurredInYears |
P9323
|
FINISHED |
| Object | 1904–1905 |
—
|
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: 1904–1905 | Statement: [Russo-Japanese War, occurredInYears, 1904–1905]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occurredInYears Context triple: [Russo-Japanese War, occurredInYears, 1904–1905]
-
A.
usedByYears
Indicates the span of years during which something (such as a method, standard, or item) was in use by a particular entity.
-
B.
coversYearsTo
Indicates a temporal relationship where one entity spans, includes, or extends up to a specified year or range of years represented by the other entity.
-
C.
occurredIn
chosen
Indicates that an event or action took place within a specific location, context, or time frame.
-
D.
durationInYears
Indicates the length of time associated with something, measured in whole or fractional years.
-
E.
appliesInYears
Indicates that something (such as a rule, condition, or effect) is valid, relevant, or in force during specific years.
- 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_69f76e885b848190bad82c87e9525486 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:13 p.m.