Triple
T8932664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armed Forces of Liberia |
E212693
|
entity |
| Predicate | restructuringPeriod |
P14846
|
FINISHED |
| Object | mid-2000s |
—
|
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: mid-2000s | Statement: [Armed Forces of Liberia, restructuringPeriod, mid-2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: restructuringPeriod Context triple: [Armed Forces of Liberia, restructuringPeriod, mid-2000s]
-
A.
reorganizationPeriod
chosen
Indicates the time span during which a structural or organizational change is planned, underway, or in effect.
-
B.
restatementPeriod
Indicates the time span over which something is restated, revised, or reissued, typically referring to a defined interval covered by a correction or updated version.
-
C.
rescissionPeriod
Indicates the time span during which a party is allowed to cancel or revoke an agreement or transaction without penalty.
-
D.
reconstructionPeriod
Indicates a time span during which something that was damaged, destroyed, or altered is being rebuilt, restored, or substantially repaired.
-
E.
reconstructionEndDate
Indicates the date on which a reconstruction process or project is completed.
- 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_69ca8395c438819087d7cb844ab5990c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc668e5c108190b08f9cd6b4fd4a8b |
completed | April 1, 2026, 12:27 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed3286c8190a21de2ee11f2639f |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:57 p.m.