Triple
T29054087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abraham Lincoln’s Ten Percent Plan |
E735340
|
entity |
| Predicate | implementedInPartIn |
P63779
|
FINISHED |
| Object | Louisiana |
—
|
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: Louisiana | Statement: [Abraham Lincoln’s Ten Percent Plan, implementedInPartIn, Louisiana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: implementedInPartIn Context triple: [Abraham Lincoln’s Ten Percent Plan, implementedInPartIn, Louisiana]
-
A.
implementedInPartBy
Indicates that the realization or execution of something is partially carried out, supported, or fulfilled by the referenced entity.
-
B.
implementedAsPartOf
chosen
Indicates that something has been realized or carried out as a component or subset of a larger implementation or project.
-
C.
isPartially
Indicates that one entity is included within another to some extent, but not completely or fully.
-
D.
partiallyIncorporatedInto
Indicates that one entity has been integrated or absorbed into another entity, but only to a limited or incomplete extent.
-
E.
partiallySupportedBy
Indicates that something receives incomplete, limited, or not fully sufficient support from another entity.
- 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_69f077e64b88819094d37bdbca8191b3 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f67f7efc3c8190986d2d95b7a23729 |
completed | May 2, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 28, 2026, 10:10 a.m.