Triple
T636858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charlotte Mint |
E16640
|
entity |
| Predicate | functionAfterCivilWar |
P17394
|
FINISHED |
| Object | assay office |
—
|
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: assay office | Statement: [Charlotte Mint, functionAfterCivilWar, assay office]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionAfterCivilWar Context triple: [Charlotte Mint, functionAfterCivilWar, assay office]
-
A.
legalStatusAfterWar
Indicates the legal condition or classification assigned to an entity as a consequence of, or following the conclusion of, a war or armed conflict.
-
B.
civilWarPeriod
Indicates a time span during which a civil war is occurring or in effect.
-
C.
afterRepublicBecame
Indicates that one event, state, or condition occurred subsequent to the time when a republic was established or came into existence.
-
D.
postwarOutcome
Indicates the result or consequences that follow for a party or situation after a war has ended.
-
E.
civilWarEnd
Indicates that an internal armed conflict within a country has come to an official or de facto conclusion.
- 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_69a4936be1c88190af56540324b57da7 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49ee7fdbc8190858e42bb1bfdb3ff |
completed | March 1, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69a49d0483908190a5ec42a7403c258e |
completed | March 1, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69a49defe58c8190bd39ef47c9f660a7 |
completed | March 1, 2026, 8:13 p.m. |
Created at: March 1, 2026, 7:35 p.m.