Triple
T17481125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Julin |
E425660
|
entity |
| Predicate | siteFeature |
P1205
|
FINISHED |
| Object | underground shafts |
—
|
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: underground shafts | Statement: [Operation Julin, siteFeature, underground shafts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: siteFeature Context triple: [Operation Julin, siteFeature, underground shafts]
-
A.
featuresIn
Indicates that an entity appears or plays a role within another entity, such as a person or element being included in a work, event, or context.
-
B.
site
chosen
Indicates that one entity is the physical or virtual location where another entity is situated, occurs, or is based.
-
C.
sceneFeature
Indicates a characteristic, element, or attribute that is present within or helps define a particular scene.
-
D.
featureType
Indicates the specific kind or category of feature that characterizes or distinguishes an entity.
-
E.
servesFeature
Indicates that one entity provides or makes available a particular feature or functionality to another entity.
- 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_69d889dccf7481909264a1844a2e9100 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451bfd75481908c20bc2c1cbff593 |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f341c88190adabe526d8903b05 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:48 a.m.