Triple
T9694468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arauco War |
E234612
|
entity |
| Predicate | significantPhaseStart |
P79945
|
FINISHED |
| Object | 1550 |
—
|
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: 1550 | Statement: [Arauco War, significantPhaseStart, 1550]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantPhaseStart Context triple: [Arauco War, significantPhaseStart, 1550]
-
A.
majorPhase
Indicates that one phase is a primary or dominant stage within a larger process, lifecycle, or sequence.
-
B.
marksPhase
chosen
Indicates that one event, state, or condition designates the beginning, end, or boundary of a particular phase in a process or sequence.
-
C.
significantAfter
Indicates that one event or state occurs after another in a way that is temporally meaningful or non-trivially later, not just immediately or insignificantly afterward.
-
D.
targetsPhase
Indicates that an action, process, or entity is specifically directed toward or intended to affect a particular phase or stage within a larger sequence or lifecycle.
-
E.
significantDevelopment
Indicates a development, change, or event that has substantial impact or importance within a given context or process.
- 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_69ca84cb580c8190a7e5f4b3bcdaf2a4 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9d348868819083aec7a5da8c455b |
completed | April 1, 2026, 10:33 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b840f081909f66bf0b66d17d9b |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:17 p.m.