Triple
T11001863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IRS-1B |
E260020
|
entity |
| Predicate | applications |
P90630
|
FINISHED |
| Object | agricultural 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: agricultural monitoring | Statement: [IRS-1B, applications, agricultural monitoring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: applications Context triple: [IRS-1B, applications, agricultural monitoring]
-
A.
commonApplication
chosen
Indicates that multiple entities share or participate in the same application, process, or usage context.
-
B.
applicationRequirement
Indicates that one entity specifies a condition or prerequisite that must be met for the use, approval, or execution of another entity or process.
-
C.
appliesVia
Indicates that an action, rule, or effect is carried out, implemented, or achieved through a specified method, medium, or mechanism.
-
D.
appliedAs
Indicates that one entity submitted itself or was put forward for consideration in a particular role, position, or context relative to another entity.
-
E.
appliedPrimarilyTo
Indicates that something is used mainly or chiefly in relation to a particular target, context, or purpose, rather than being used broadly or equally elsewhere.
- 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_69d6aa8a6a548190a750f944ccdc8064 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d796d760008190930228fa77b61b8b |
completed | April 9, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69d72e96be6c8190a46c69f61b2d8cd4 |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:25 p.m.