Triple
T24721259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Agrarians |
E612301
|
entity |
| Predicate | keyTextType |
P21838
|
FINISHED |
| Object | manifesto |
—
|
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: manifesto | Statement: [Southern Agrarians, keyTextType, manifesto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyTextType Context triple: [Southern Agrarians, keyTextType, manifesto]
-
A.
keyText
Indicates that a piece of text functions as a key or identifier used to access, reference, or unlock something in a system or context.
-
B.
keyType
chosen
Indicates the classification or category of a key in relation to how it is used or defined within a system or context.
-
C.
keyParameter
Indicates that one entity functions as a primary or critical parameter that significantly influences or determines the behavior, outcome, or configuration of another entity.
-
D.
keyActionType
Indicates the specific kind of action or operation being performed or associated with a key.
-
E.
keyContext
Indicates that one entity provides the primary contextual framework or background within which another entity is interpreted, used, or understood.
- 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_69e2d7d6e7a48190bb43b0d8bb1137a0 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f410fe3b848190ae296a29f742ee30 |
completed | May 1, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f40ee8ada8819089a7016b50308ff0 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 3:40 a.m.