Triple
T18494414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John "Jack" Young |
E451902
|
entity |
| Predicate | likelyOccupation |
P66757
|
FINISHED |
| Object | early settler |
—
|
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: early settler | Statement: [John "Jack" Young, likelyOccupation, early settler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: likelyOccupation Context triple: [John "Jack" Young, likelyOccupation, early settler]
-
A.
subjectOccupation
Indicates that the subject holds or performs a particular job, profession, or role as their occupation.
-
B.
occupationType
Indicates the specific kind or category of work, profession, or role that an entity performs or holds.
-
C.
natureOfOccupation
Indicates the type or character of a person's occupation, describing what kind of work or role it is rather than who performs it.
-
D.
allegedOccupation
chosen
Indicates that one entity is claimed or reported to be the occupation or job role of another entity, without asserting that this claim is necessarily true.
-
E.
requiredOccupationOf
Indicates that one entity specifies the occupation or job role that is required or expected for another entity (such as a position, task, or qualification).
- 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_69d8d3855d50819097fc8561b0299dd9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e532bf206c8190a146cd1abd752152 |
completed | April 19, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69e469dbf5208190b6fc49e02a087f54 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:35 a.m.