Triple
T8888449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fermor |
E211592
|
entity |
| Predicate | hasOriginInOccupation |
P8625
|
FINISHED |
| Object | agriculture |
—
|
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: agriculture | Statement: [Fermor, hasOriginInOccupation, agriculture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginInOccupation Context triple: [Fermor, hasOriginInOccupation, agriculture]
-
A.
derivesFromOccupation
chosen
Indicates that one entity originates from, is obtained through, or is a result of another entity’s occupation or professional role.
-
B.
endedOccupationOf
Indicates that one entity brought another entity’s occupation or control of a place or position to an end.
-
C.
isOccupationalFormOf
Indicates that one occupation is a specific form, variant, or specialization of another, more general occupation.
-
D.
earlierOccupation
Indicates that one occupation held by an entity occurred before another occupation in that entity’s work history.
-
E.
usedByOccupation
Indicates that something (such as a tool, method, or resource) is utilized in the performance of a particular occupation or job.
- 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_69ca83907954819096d52a245b635841 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc618e58d08190be3ebcbe3701b1db |
completed | April 1, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69cc5c2aec04819093c932fe51c0f08d |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:53 p.m.