Triple
T33753586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vinalhaven Island |
E864911
|
entity |
| Predicate | hasHistoricalExport |
P18134
|
FINISHED |
| Object | building stone |
—
|
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: building stone | Statement: [Vinalhaven Island, hasHistoricalExport, building stone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricalExport Context triple: [Vinalhaven Island, hasHistoricalExport, building stone]
-
A.
historicalExport
chosen
Indicates that an entity was exported from one place to another during a past or historically significant period.
-
B.
hasHistoricalData
Indicates that an entity possesses recorded information or records about past events, states, or values relevant to it.
-
C.
hasHistoricalDetail
Indicates that something includes or is associated with specific information about past events, contexts, or developments.
-
D.
hasHistoricalService
Indicates that an entity has previously provided service or fulfilled a role during a past historical period or event.
-
E.
hasHistoricalEntity
Indicates a relationship where one entity includes, references, or is associated with another entity that existed or is defined in a past historical 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_69f3498c35f881909df279ae4270f831 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fee25dbca481909e6f1c255122b3a8 |
completed | May 9, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69fee1c8915c8190b08b63e42881f1a9 |
completed | May 9, 2026, 7:27 a.m. |
Created at: May 1, 2026, 1:45 a.m.