Triple
T32311219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Negro Fort |
E825504
|
entity |
| Predicate | afterAbandonmentBecame |
P178641
|
FINISHED |
| Object | maroon community stronghold |
—
|
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: maroon community stronghold | Statement: [Negro Fort, afterAbandonmentBecame, maroon community stronghold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: afterAbandonmentBecame Context triple: [Negro Fort, afterAbandonmentBecame, maroon community stronghold]
-
A.
abandonedDuring
Indicates that one entity ceased support for or deserted another entity in the midst of an ongoing process, event, or period.
-
B.
abandonedBefore
Indicates that one entity ceased or gave up on something prior in time to another entity doing so.
-
C.
abandonedAfterEvent
Indicates that one entity ceased support for, left, or discontinued involvement with another entity following a specific event or occurrence.
-
D.
abandonedBy
Indicates that one entity has been deserted, forsaken, or left behind by another entity that was previously present, responsible, or involved.
-
E.
periodOfAbandonment
Indicates a time span during which something is left unused, unattended, or not maintained.
- 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_69f3491213b88190a57094d8697a7455 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
| PDg | Predicate description generation | batch_69f7117cf2188190b29e36fc1e342c60 |
completed | May 3, 2026, 9:12 a.m. |
Created at: May 1, 2026, 12:46 a.m.