Triple
T14138014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Party System |
E350348
|
entity |
| Predicate | regionallyDistinctPatterns |
P112957
|
FINISHED |
| Object | North |
—
|
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: North | Statement: [Second Party System, regionallyDistinctPatterns, North]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionallyDistinctPatterns Context triple: [Second Party System, regionallyDistinctPatterns, North]
-
A.
regionallyDistinctFrom
Indicates that two entities differ from each other in characteristics or classification based on their geographic or regional context.
-
B.
regionSpecialization
Indicates that a region is designated or recognized as being particularly focused on, adapted to, or specialized in a specific function, activity, or domain.
-
C.
regionShaped
Indicates that one region determines or influences the shape or form of another region.
-
D.
regionCodePattern
Indicates the standardized format or pattern that valid region codes must follow.
-
E.
regionallySymbolicIn
Indicates that something serves as a symbol or emblem specifically within a particular region or geographic area.
- 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_69d827865f608190b311820428ae027b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de610fb86c81909eb26bf9c13696ca |
completed | April 14, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69de05b5e7a08190a16be9ad8b92b80c |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239a02e881909b0e2679487e4ab2 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 10, 2026, 12:38 a.m.