Triple
T15936670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Monitoring System |
E386456
|
entity |
| Predicate | monitorsMedium |
P121055
|
FINISHED |
| Object | earth |
—
|
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: earth | Statement: [International Monitoring System, monitorsMedium, earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monitorsMedium Context triple: [International Monitoring System, monitorsMedium, earth]
-
A.
monitors
Indicates that one entity observes, tracks, or checks the state, behavior, or performance of another entity over time.
-
B.
typicalMonitor
Indicates that one entity commonly or characteristically monitors, observes, or oversees another entity in a usual or expected manner.
-
C.
mediumDisplayed
Indicates that a particular medium (such as an image, video, or document) is being shown or rendered in a given context or interface.
-
D.
mediumAppearance
Indicates that an entity appears in or is featured within a particular medium (such as a work, format, or communication channel).
-
E.
medium
Indicates that an entity serves as the means, channel, or intermediary through which an action, communication, or effect is carried out between other entities.
- 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_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. |
| PDg | Predicate description generation | batch_69e17d48cc9c8190b03fd07ae2e9dfd8 |
completed | April 17, 2026, 12:22 a.m. |
Created at: April 10, 2026, 4:53 a.m.