Triple
T2421981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epistle to Titus |
E53437
|
entity |
| Predicate | containsHouseholdCodeFor |
P38470
|
FINISHED |
| Object | older men |
—
|
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: older men | Statement: [Epistle to Titus, containsHouseholdCodeFor, older men]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsHouseholdCodeFor Context triple: [Epistle to Titus, containsHouseholdCodeFor, older men]
-
A.
hasHouseholdType
Indicates the type or category of household associated with an entity (e.g., family, single-person, shared, etc.).
-
B.
hasMunicipalityCode
Indicates that an entity is associated with a specific official municipality code used for administrative or identification purposes.
-
C.
hasHouseNumberForOECD
Indicates that an entity is assigned a specific house number according to an OECD-related addressing or data standard.
-
D.
containsFamily
Indicates that one entity includes or encompasses members of a particular family group within it.
-
E.
hasParentHouse
Indicates that an entity is associated with or belongs to a specific parent house within a hierarchical or familial structure.
- F. None of above. chosen
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_69ab495c44d48190b7235b23719bc3f6 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abc9f342e88190a430b02842ded418 |
completed | March 7, 2026, 6:47 a.m. |
| PD | Predicate disambiguation | batch_69abc5a889948190b77de4ef6ac815a8 |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abc9f1ba608190b488874bed3533dd |
completed | March 7, 2026, 6:47 a.m. |
Created at: March 6, 2026, 9:42 p.m.