Triple
T24995091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Odawara Castle |
E625546
|
entity |
| Predicate | controlledDuringPeriod |
P20308
|
FINISHED |
| Object | Sengoku period |
—
|
NE NERFINISHED |
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: Sengoku period | Statement: [Odawara Castle, controlledDuringPeriod, Sengoku period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlledDuringPeriod Context triple: [Odawara Castle, controlledDuringPeriod, Sengoku period]
-
A.
controlledSince
Indicates that one entity has held control or authority over another entity starting from a specified point in time.
-
B.
controlledAfter
Indicates that one entity gains or maintains control over another entity only after a specified time, event, or condition has occurred.
-
C.
usedDuring
Indicates that one entity is employed, applied, or active in the course of another entity’s process, event, or time period.
-
D.
suppressedDuring
Indicates that one event, action, or state is actively prevented, inhibited, or held back while another specified event, condition, or time period is occurring.
-
E.
ownedDuring
chosen
Indicates that one entity possessed or held ownership of another entity for some or all of a specified time interval.
- 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_69e2ff2611c081908710457fbe6d376b |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620dc38088190b56b2b15ed75b3c2 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 18, 2026, 6:04 a.m.