Triple
T21892371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valley, Nova Scotia |
E540583
|
entity |
| Predicate | hasNearbyFarms |
P93890
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Valley, Nova Scotia, hasNearbyFarms, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyFarms Context triple: [Valley, Nova Scotia, hasNearbyFarms, true]
-
A.
hasNearbyHorseFarm
Indicates that one entity is located close to or in the vicinity of a horse farm.
-
B.
hasNearbyAgriculturalActivity
chosen
Indicates that an entity is located close enough to agricultural operations or land use for those activities to be considered relevant or influential to it.
-
C.
hasNotableFarm
Indicates that an entity possesses or is associated with a farm that is considered notable or significant in some recognized way.
-
D.
hasFarm
Indicates that one entity owns, operates, or is responsible for a farm associated with another entity.
-
E.
servesAsFarmSystemFor
Indicates that one entity functions as a developmental or feeder system that supplies trained or prepared resources (such as players, talent, or products) to another entity.
- 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_69e0c47a95908190ae3e19b716accb3d |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f11fc46dd481908a119cfbe26564a3 |
completed | April 28, 2026, 8:59 p.m. |
| PD | Predicate disambiguation | batch_69e6be9a65888190a66598d62d20366c |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:06 p.m.