Triple
T4664547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kols |
E102812
|
entity |
| Predicate | relationshipToLand |
P57406
|
FINISHED |
| Object | small-scale subsistence farming |
—
|
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: small-scale subsistence farming | Statement: [Kols, relationshipToLand, small-scale subsistence farming]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToLand Context triple: [Kols, relationshipToLand, small-scale subsistence farming]
-
A.
landRelation
chosen
Indicates a spatial or ownership-based relationship between entities and a specific piece or area of land.
-
B.
relationToMLS
Indicates a relationship or association that an entity has with a specific MLS (Multiple Listing Service) system or record.
-
C.
termRelationTo
Indicates a general relational association between one term and another, without specifying the exact nature of that relationship.
-
D.
relationshipToState
Indicates a relationship or connection that an entity has with a particular state or governmental body.
-
E.
relationshipType
Indicates the specific kind of relationship that exists between two or more entities.
- 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_69bd43d9cba4819086c1ab1c2d9d2133 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd655aceb081908100ffc0498fe183 |
completed | March 20, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69bd6215864c8190b50ba0f63ba87d0c |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:15 p.m.