Triple
T23377254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy League (France) |
E593640
|
entity |
| Predicate | significantReorganizationDate |
P44327
|
FINISHED |
| Object | 1584 |
—
|
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: 1584 | Statement: [Holy League (France), significantReorganizationDate, 1584]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantReorganizationDate Context triple: [Holy League (France), significantReorganizationDate, 1584]
-
A.
reorganizationYear
chosen
Indicates the year in which an entity underwent a structural or organizational reorganization.
-
B.
reclassifiedDate
Indicates the date on which something’s classification or status was changed from its previous category to a new one.
-
C.
furtherReorganizedOn
Indicates that an entity was reorganized again or to a greater extent on a specified later date or occasion.
-
D.
reorganizationPeriod
Indicates the time span during which a structural or organizational change is planned, underway, or in effect.
-
E.
consolidationDate
Indicates the date on which multiple entities, records, or accounts are formally combined into a single consolidated whole.
- 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_69e25d268a50819095f2fd479da8ef3f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a3b3cc348190953d0b0ebac9c5dd |
completed | April 29, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69f061c7aaa48190a58ce93f87155ffc |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:33 p.m.