Triple
T22629761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2,4-D |
E558515
|
entity |
| Predicate | hasSoilMobility |
P42725
|
FINISHED |
| Object | moderately mobile |
—
|
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: moderately mobile | Statement: [2,4-D, hasSoilMobility, moderately mobile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSoilMobility Context triple: [2,4-D, hasSoilMobility, moderately mobile]
-
A.
hasSoilProperty
chosen
Indicates that a soil entity possesses or is characterized by a specific soil-related property or attribute.
-
B.
hasSoil
Indicates that one entity possesses, contains, or is associated with a particular type or instance of soil.
-
C.
hasRegolithBehavior
Indicates that an entity exhibits or is associated with a specific type of behavior related to regolith (loose surface material such as soil, dust, or broken rock).
-
D.
hasSoilColor
Indicates that an entity possesses soil characterized by a specific color.
-
E.
soilRepresents
Indicates that one soil sample, type, or condition stands for, symbolizes, or serves as a proxy for another soil-related state or concept.
- 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_69e245467d9881908d6985bd0db7a1f1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f16e3febd081909ff21abef1e4035d |
completed | April 29, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69ee62855558819080da946c7b35a160 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 3:02 p.m.