Triple
T16030219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seil |
E388826
|
entity |
| Predicate | historicExport |
P18134
|
FINISHED |
| Object | roofing slate |
—
|
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: roofing slate | Statement: [Seil, historicExport, roofing slate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicExport Context triple: [Seil, historicExport, roofing slate]
-
A.
historicalExport
chosen
Indicates that an entity was exported from one place to another during a past or historically significant period.
-
B.
historicFor
Indicates that something holds historical significance or importance specifically in relation to another entity.
-
C.
historicActivity
Indicates that an entity engaged in an activity or event of historical significance in the past.
-
D.
historicalExploration
Indicates that an entity has engaged in or is associated with the act of exploring or investigating something in the past.
-
E.
historicManager
Indicates that an entity previously held a managerial role or position over another entity during a past period.
- 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_69d86dada3808190825d5f80d72fbe88 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1858a00888190b8505071575dc56f |
completed | April 17, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e1826a4f7c8190aba6d4f1075141b0 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:56 a.m.