Triple
T21474294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PHI |
E529812
|
entity |
| Predicate | scopeOfSignificance |
P25607
|
FINISHED |
| Object | local historical significance |
—
|
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: local historical significance | Statement: [PHI, scopeOfSignificance, local historical significance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scopeOfSignificance Context triple: [PHI, scopeOfSignificance, local historical significance]
-
A.
scopeOfContribution
Indicates the specific area, domain, or extent within which an entity’s contribution or involvement applies.
-
B.
typeOfSignificance
Indicates that one entity specifies the nature or category of importance, relevance, or significance that another entity possesses.
-
C.
fieldOfSignificance
Indicates that something holds particular importance, relevance, or impact within a specified domain, context, or area of interest.
-
D.
scopeType
chosen
Indicates the specific range, level, or context within which a given relationship, rule, or action is defined or applies.
-
E.
significance
Indicates that one entity holds particular importance, influence, or meaningful impact in relation to another entity or context.
- 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_69e0c459acb481909bb6ee452a0045c7 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea1650788190bd55ebdbf1dfc46f |
completed | April 23, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69e631ec1d048190b6da97da8222e413 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:19 p.m.