Triple
T15936636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Monitoring System |
E386456
|
entity |
| Predicate | hasMonitoringTechnology |
P80146
|
FINISHED |
| Object | seismic monitoring |
—
|
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: seismic monitoring | Statement: [International Monitoring System, hasMonitoringTechnology, seismic monitoring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMonitoringTechnology Context triple: [International Monitoring System, hasMonitoringTechnology, seismic monitoring]
-
A.
canBeMonitoredWith
chosen
Indicates that one entity is suitable or able to be observed, tracked, or supervised using another specified entity or method.
-
B.
hasNavigationTechnology
Indicates that an entity is equipped with or utilizes a system or technology for determining or guiding its position, route, or movement.
-
C.
isMonitored
Indicates that an entity is being actively observed, tracked, or supervised by another entity or system.
-
D.
hasSensor
Indicates that one entity is equipped with, contains, or uses a particular sensor.
-
E.
supportsRealTimeMonitoring
Indicates that an entity provides the capability to observe and track relevant data or events continuously as they occur in real time.
- 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_69d86da750008190987eb26be3f6c118 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4d08f481909f38b75e3f42d9ab |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142d37cd88190ab50760f1783e20c |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:53 a.m.