Triple
T18990321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Irish Sea Basin system |
E464664
|
entity |
| Predicate | sealRocks |
P134055
|
FINISHED |
| Object | Triassic mudstones |
—
|
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: Triassic mudstones | Statement: [East Irish Sea Basin system, sealRocks, Triassic mudstones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sealRocks Context triple: [East Irish Sea Basin system, sealRocks, Triassic mudstones]
-
A.
seal
Indicates that an agent closes or fastens something so that it is securely shut and often airtight or watertight.
-
B.
sealType
Indicates the specific kind or category of seal associated with an entity or connection.
-
C.
sealDepiction
Indicates that one entity is a depiction or representation found on a seal associated with another entity.
-
D.
seaCode
Indicates a standardized code or identifier assigned to a sea or maritime area.
-
E.
usedSeal
Indicates that an entity has applied or employed a seal (e.g., for closure, authentication, or protection) on another entity.
- F. None of above. chosen
Provenance (4 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_69d8dd01a56c81909694a128c66b21d7 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6632cb08190a28f6ab74c2156d8 |
completed | April 20, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f88e0c81908cb20f08bf24cd32 |
completed | April 19, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69e4ad8e075c8190ad561edc5e520057 |
completed | April 19, 2026, 10:25 a.m. |
Created at: April 10, 2026, 12:01 p.m.