Triple
T19072114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parable of the Sower |
E466816
|
entity |
| Predicate | goodSoilRepresents |
P134194
|
FINISHED |
| Object | those who hear the word and understand it |
—
|
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: those who hear the word and understand it | Statement: [Parable of the Sower, goodSoilRepresents, those who hear the word and understand it]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goodSoilRepresents Context triple: [Parable of the Sower, goodSoilRepresents, those who hear the word and understand it]
-
A.
hasSoil
Indicates that one entity possesses, contains, or is associated with a particular type or instance of soil.
-
B.
soilFertility
Indicates the level or quality of nutrients and conditions in soil that affect its ability to support plant growth.
-
C.
soilOrigin
Indicates the source or provenance from which a given soil was formed or obtained.
-
D.
soilPreference
Indicates the type or condition of soil that an entity prefers or is best suited to grow or exist in.
-
E.
hasSoilProperty
Indicates that a soil entity possesses or is characterized by a specific soil-related property or attribute.
- 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e19fa6948190bdf8e8ec022e12f2 |
completed | April 20, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69e4b99f602881909eeb9c780597e0e6 |
completed | April 19, 2026, 11:16 a.m. |
| PDg | Predicate description generation | batch_69e4bfe8a06081909fd5c28a33e9f218 |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:04 p.m.