Triple
T30682791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vermont independence movement |
E781100
|
entity |
| Predicate | gainedVisibility |
P101622
|
FINISHED |
| Object | early 21st century |
—
|
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: early 21st century | Statement: [Vermont independence movement, gainedVisibility, early 21st century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gainedVisibility Context triple: [Vermont independence movement, gainedVisibility, early 21st century]
-
A.
gainedVisibilityIn
chosen
Indicates that an entity became more publicly known, noticeable, or prominent within a particular context, medium, or audience.
-
B.
gainedVisibilityThrough
Indicates that one entity became more visible, prominent, or well-known as a result of another entity or mechanism.
-
C.
visibleAfter
Indicates that one entity becomes perceptible or can be seen only after another specified event, time, or condition has occurred.
-
D.
visibleAt
Indicates that one entity can be seen or perceived from a specific location, viewpoint, or context at a given time.
-
E.
hasVisibility
Indicates that one entity can perceive, view, or access another entity or its information under certain conditions.
- 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_69f224a92f54819095499b4d32bd5134 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68b81f12c8190a0aaacc0a54f9db5 |
completed | May 2, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:33 p.m.