Triple
T19005679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Carolina Regulators |
E465072
|
entity |
| Predicate | dateOfConflict |
P134099
|
FINISHED |
| Object | 16 May 1771 |
—
|
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: 16 May 1771 | Statement: [North Carolina Regulators, dateOfConflict, 16 May 1771]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfConflict Context triple: [North Carolina Regulators, dateOfConflict, 16 May 1771]
-
A.
yearInConflict
Indicates the specific year or years during which a given conflict took place or was actively ongoing.
-
B.
conflictBeganInYear
Indicates that the specified conflict started or first broke out in the given calendar year.
-
C.
yearOfBattle
Indicates the specific calendar year in which a particular battle took place.
-
D.
conflictEndYear
Indicates the calendar year in which a particular conflict, dispute, or war came to an end.
-
E.
startOfMajorConflict
Indicates that one event marks the beginning or initial outbreak of a major conflict between parties.
- 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_69d8dd01a56c81909694a128c66b21d7 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6a494688190a277b2cddf300235 |
completed | April 20, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f88e0c81908cb20f08bf24cd32 |
completed | April 19, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69e4ad8e075c8190ad561edc5e520057 |
completed | April 19, 2026, 10:25 a.m. |
Created at: April 10, 2026, 12:01 p.m.