Triple
T1183757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Order of Isabella the Catholic |
E25197
|
entity |
| Predicate | reformedIn |
P4888
|
FINISHED |
| Object | 1847 |
—
|
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: 1847 | Statement: [Order of Isabella the Catholic, reformedIn, 1847]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reformedIn Context triple: [Order of Isabella the Catholic, reformedIn, 1847]
-
A.
reformedOffice
Indicates that an office or official position has been reorganized, restructured, or fundamentally changed from its previous form.
-
B.
reform
chosen
Indicates bringing about significant changes to an existing system, practice, or entity in order to improve or correct it.
-
C.
denominationReform
Indicates a change or restructuring in a religious denomination’s doctrines, practices, or organizational form.
-
D.
notableReform
Indicates that an entity is recognized for having initiated, led, or been central to a significant reform or transformative change in a system, policy, or institution.
-
E.
refoundedBy
Indicates that an entity was re-established or reconstituted by another entity after a period of inactivity, dissolution, or significant change.
- 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_69a494267b4c819088c97a59182bf56a |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd37b4a88190bb71a2d272c5fd1a |
completed | March 1, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69a4bb59ca6c81908597a81646674aaa |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.