Triple
T14384561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maximilien Morrel |
E356688
|
entity |
| Predicate | hasFatherOccupationContext |
P2600
|
FINISHED |
| Object | shipowner’s son |
—
|
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: shipowner’s son | Statement: [Maximilien Morrel, hasFatherOccupationContext, shipowner’s son]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFatherOccupationContext Context triple: [Maximilien Morrel, hasFatherOccupationContext, shipowner’s son]
-
A.
hasFatherEmployer
Indicates that the employer of a person’s father is related to or associated with that person.
-
B.
fatherOccupation
chosen
Indicates the type of job or profession held by a person's father.
-
C.
hasOccupationRelative
Indicates that one entity has another entity as a relative who holds a particular occupation or job.
-
D.
parentOccupation
Indicates that one entity has an occupation which is the job or profession of the other entity’s parent.
-
E.
derivesFromOccupation
Indicates that one entity originates from, is obtained through, or is a result of another entity’s occupation or professional role.
- 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_69d827927c988190ad98bb0360981783 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de9025cff881908c08224d90d9f750 |
completed | April 14, 2026, 7:06 p.m. |
| PD | Predicate disambiguation | batch_69de2aa024c48190805df6a9d63deb10 |
completed | April 14, 2026, 11:53 a.m. |
Created at: April 10, 2026, 1:16 a.m.