Triple
T21583708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French conquest of Corsica |
E532584
|
entity |
| Predicate | hasResultingStatus |
P116090
|
FINISHED |
| Object | Corsica becomes a French province |
—
|
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: Corsica becomes a French province | Statement: [French conquest of Corsica, hasResultingStatus, Corsica becomes a French province]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResultingStatus Context triple: [French conquest of Corsica, hasResultingStatus, Corsica becomes a French province]
-
A.
hasOutputStatus
Indicates that an entity is associated with a particular state or condition of its produced output.
-
B.
hasResultingChange
Indicates that one entity causes or leads to a specific change or transformation in another entity or state.
-
C.
hasStatusBasedOn
chosen
Indicates that an entity’s status is determined or derived from another condition, event, or entity.
-
D.
hasOutcomeIndicator
Indicates that something is associated with a specific measure or indicator used to evaluate its outcome or results.
-
E.
hasStatusIn
Indicates that an entity holds or is assigned a particular status within a specified context, scope, or system.
- 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_69e0c4618bec8190bcb0feb74568cbb1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eeeb5e45b48190a52346f6484c6f84 |
completed | April 27, 2026, 4:51 a.m. |
| PD | Predicate disambiguation | batch_69e632109d048190b4ac3f14fe48d1a0 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:31 p.m.