Triple
T29621899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry IX (Jacobite) |
E755017
|
entity |
| Predicate | lostFortuneDueTo |
P167519
|
FINISHED |
| Object | French Revolution |
—
|
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: French Revolution | Statement: [Henry IX (Jacobite), lostFortuneDueTo, French Revolution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lostFortuneDueTo Context triple: [Henry IX (Jacobite), lostFortuneDueTo, French Revolution]
-
A.
capitalOverlooked
Indicates that a capital city is being ignored, undervalued, or not given due attention or recognition in a given context.
-
B.
lostIn
Indicates that an entity has become unable to find its way or is no longer in control or possession within a particular place, situation, or context.
-
C.
lostAfterDiscovery
Indicates that something ceased to be possessed or went missing after it had already been found or discovered.
-
D.
treasureInvolved
Indicates that a situation, event, or action involves or is related to treasure in some significant way.
-
E.
lost
Indicates that an entity no longer possesses or has been deprived of another entity it previously had.
- F. None of above. chosen
Provenance (4 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_69f0ef86b6ec8190a87fff07fd983b1e |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66e250e408190af182202f0e328aa |
completed | May 2, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 6:35 p.m.