Triple
T25811440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council of Marine |
E650121
|
entity |
| Predicate | replacesPosition |
P29646
|
FINISHED |
| Object | ministerial system |
—
|
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: ministerial system | Statement: [Council of Marine, replacesPosition, ministerial system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacesPosition Context triple: [Council of Marine, replacesPosition, ministerial system]
-
A.
placedBy
Indicates that one entity was positioned, set, or put in a location or context by another entity.
-
B.
replacedWith
chosen
Indicates that one entity has been substituted or superseded by another entity, taking over its role, function, or position.
-
C.
seeksToReplace
Indicates an intention or effort by one entity to take over the role, function, or position currently held by another entity.
-
D.
replacesComponentOf
Indicates that one entity takes the place of a specific component within another entity, substituting for that component in its role or function.
-
E.
replacedAtPar
Indicates that one entity has been replaced by another at a specific location or position within a larger structure or sequence.
- 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_69e7ab35d264819095367f7e80c983ff |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 22, 2026, 7:10 a.m.