Triple
T2579567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern redbud |
E57055
|
entity |
| Predicate | soilPHPreference |
P2070
|
FINISHED |
| Object | neutral to alkaline |
—
|
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: neutral to alkaline | Statement: [Eastern redbud, soilPHPreference, neutral to alkaline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soilPHPreference Context triple: [Eastern redbud, soilPHPreference, neutral to alkaline]
-
A.
soilPreference
Indicates the type or condition of soil that an entity prefers or is best suited to grow or exist in.
-
B.
hasSoil
Indicates that one entity possesses, contains, or is associated with a particular type or instance of soil.
-
C.
acidityLevel
chosen
Indicates the degree or intensity of acidity associated with an entity, typically measured by pH or a comparable scale.
-
D.
plantingStyle
Indicates the method or arrangement used to plant entities in relation to each other or their environment.
-
E.
substratePreference
Indicates a relationship where an entity tends to occur on, grow in, or utilize a particular physical material or medium as its preferred substrate.
- 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_69ab4a4dca6481908c301f8e317396e7 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd3a9fd3c8190a521931e40cd801c |
completed | March 7, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69abd0cfeae08190aed03866ba071c5c |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:49 p.m.