Triple
T3602380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Empress Irene of Athens |
E76285
|
entity |
| Predicate | householdOrigin |
P50173
|
FINISHED |
| Object | noble family of Athens |
—
|
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: noble family of Athens | Statement: [Empress Irene of Athens, householdOrigin, noble family of Athens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: householdOrigin Context triple: [Empress Irene of Athens, householdOrigin, noble family of Athens]
-
A.
household
Indicates that two or more entities belong to or are part of the same household unit, typically sharing a residence and domestic life.
-
B.
houseFounded
Indicates that an entity (such as a house, organization, or lineage) was established or created by another entity or at a specific time.
-
C.
originalHomeland
Indicates the place or region that is considered the ancestral or earliest homeland of an entity.
-
D.
historicalOrigin
Indicates the relationship by which one entity serves as the source, origin, or starting point in history for another entity.
-
E.
familyContext
Indicates that the entities are related or associated within a family or household context, such as kinship, caregiving, or shared domestic life.
- 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_69ad85d93dcc819094fba90cf70f4996 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc1dd264c819098796f5f50f251be |
completed | March 8, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69adb83b66708190bb9d2f23d6fd308e |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb9261a948190b67f6c6ac0dae2e9 |
completed | March 8, 2026, 6 p.m. |
Created at: March 8, 2026, 3:22 p.m.