Triple
T21775859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scandinavianism movement |
E537572
|
entity |
| Predicate | prominentSupportBase |
P34846
|
FINISHED |
| Object | students |
—
|
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: students | Statement: [Scandinavianism movement, prominentSupportBase, students]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prominentSupportBase Context triple: [Scandinavianism movement, prominentSupportBase, students]
-
A.
mainSupportBase
chosen
Indicates that one entity serves as the primary structural or functional support base for another entity.
-
B.
notableSupportBaseCharacteristic
Indicates that a subject’s base of support is distinguished by a particular notable characteristic or quality.
-
C.
hasSupportBaseIn
Indicates that one entity maintains an operational or organizational base of support located in another entity.
-
D.
IndependentSupportBase
Indicates that one entity serves as a foundational, self-sufficient support structure for another, not relying on additional supports or connections.
-
E.
notableBase
Indicates that a particular location serves as a significant or distinguished base or headquarters for an entity.
- 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_69e0c470759c819094a215757113562b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f046291d808190b5111a8d4819909f |
completed | April 28, 2026, 5:31 a.m. |
| PD | Predicate disambiguation | batch_69e6be6299988190a34c98fa76d94700 |
completed | April 21, 2026, 12:01 a.m. |
Created at: April 16, 2026, 6:51 p.m.