Triple
T18817578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whin Sill dolerite |
E460176
|
entity |
| Predicate | intrusionStyle |
P133535
|
FINISHED |
| Object | sill |
—
|
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: sill | Statement: [Whin Sill dolerite, intrusionStyle, sill]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intrusionStyle Context triple: [Whin Sill dolerite, intrusionStyle, sill]
-
A.
methodOfInfiltration
Indicates the specific technique or approach used to secretly gain access to or penetrate a target, system, or organization.
-
B.
intrudedInto
Indicates that one entity has entered or encroached upon another entity’s space, domain, or context without permission or in an unwelcome manner.
-
C.
isInvasive
Indicates that one entity intrudes upon, spreads into, or encroaches on another entity or environment in a disruptive or unwanted manner.
-
D.
methodOfInvasion
Indicates the specific way or technique by which an invasion is carried out.
-
E.
infiltratedBy
Indicates that an entity has been secretly entered, penetrated, or taken over by another entity, typically in a covert or unauthorized manner.
- 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_69d8dcf94c288190a06dea029ae4b223 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5a6b7e75c81909bc65cfc61cbe1c6 |
completed | April 20, 2026, 4:08 a.m. |
| PD | Predicate disambiguation | batch_69e48d1b10ec8190985c6fb5766ff981 |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49a9bcc0c81908df3e513fd6762ff |
completed | April 19, 2026, 9:04 a.m. |
Created at: April 10, 2026, 11:55 a.m.