Triple
T32866048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adam Macy |
E840650
|
entity |
| Predicate | associatedWithFarm |
P57125
|
FINISHED |
| Object | Home Farm |
E409416
|
NE 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: Home Farm | Statement: [Adam Macy, associatedWithFarm, Home Farm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithFarm Context triple: [Adam Macy, associatedWithFarm, Home Farm]
-
A.
hasFarm
Indicates that one entity owns, operates, or is responsible for a farm associated with another entity.
-
B.
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.
-
C.
hasAgriculturalAssociation
Indicates that there exists a formal or recognized connection between an entity and an agricultural organization, group, or activity.
-
D.
hasNotableFarm
chosen
Indicates that an entity possesses or is associated with a farm that is considered notable or significant in some recognized way.
-
E.
associatedWithAnimal
Indicates a relationship where an entity has a connection, link, or relevance to an animal.
- F. None of above.
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_69f34942465c819099b3fb47f9044f58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34c67a82748190939936dab4a97543 |
completed | June 19, 2026, 4:32 a.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:17 a.m.