Triple
T7296588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salad Bowl of the World |
E164536
|
entity |
| Predicate | hasNotableCrop |
P55351
|
FINISHED |
| Object | lettuce |
—
|
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: lettuce | Statement: [Salad Bowl of the World, hasNotableCrop, lettuce]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableCrop Context triple: [Salad Bowl of the World, hasNotableCrop, lettuce]
-
A.
hasNotableFarm
Indicates that an entity possesses or is associated with a farm that is considered notable or significant in some recognized way.
-
B.
hasCropSpecies
Indicates that a particular location, field, or agricultural system is associated with or used to cultivate a specified crop species.
-
C.
containsEdibleCrop
Indicates that one entity includes within it or has present an edible crop as part of its contents or composition.
-
D.
notableCrop
chosen
Indicates that a particular crop is especially significant, prominent, or characteristic in relation to the referenced entity.
-
E.
isCultivatedAs
Indicates that one entity is intentionally grown, tended, or produced by another as a crop, resource, or cultivated organism.
- 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_69c6887a499881909dd23341399c59d8 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6eb8e48d48190ada4d507f3b61bc4 |
completed | March 27, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69c6e76e67d88190bd3ca6864f45845a |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3 p.m.