Triple
T18619866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steward |
E455118
|
entity |
| Predicate | isOccupationalTitleFor |
P38371
|
FINISHED |
| Object | person who managed a household |
—
|
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: person who managed a household | Statement: [Steward, isOccupationalTitleFor, person who managed a household]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOccupationalTitleFor Context triple: [Steward, isOccupationalTitleFor, person who managed a household]
-
A.
isOccupationalFormOf
Indicates that one occupation is a specific form, variant, or specialization of another, more general occupation.
-
B.
occupationalNameFor
chosen
Indicates that one entity is the name or label used to denote the occupation or profession of another entity.
-
C.
refersToWorkTitleAbbreviationOf
Indicates that one entity refers to a work by using an abbreviated form of that work’s title.
-
D.
hasProfessionalTitleAuthority
Indicates that an entity has the formal authority to grant, assign, or recognize professional titles for other entities.
-
E.
isOccupationalSurname
Indicates that a surname originates from or is derived from a person’s occupation or trade.
- 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_69d8d38bbe7c8190bdec3138e7d413c9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54f00889c8190931f8d3fbabd531b |
completed | April 19, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69e478d4a7948190a4bb9223bb5dddfc |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:46 a.m.