Triple
T31251845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Padre |
E796843
|
entity |
| Predicate | hasHumanSubject |
P172206
|
FINISHED |
| Object | family relationships |
—
|
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: family relationships | Statement: [Padre, hasHumanSubject, family relationships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHumanSubject Context triple: [Padre, hasHumanSubject, family relationships]
-
A.
hasTypicalSubject
Indicates that something is commonly or characteristically used as the subject (agent or topic) of a given relation or action.
-
B.
hasNotableSubject
Indicates that an entity is associated with a subject that is particularly significant, prominent, or noteworthy in relation to it.
-
C.
hasSubjectPlace
Indicates that something is associated with or occurs in a particular subject-related place or location.
-
D.
hasSubjectPronouns
Indicates that an entity is associated with one or more pronouns that function as its grammatical subject in sentences.
-
E.
hasPrimarySubject
Indicates that an entity is the main or principal subject associated with another entity or resource.
- 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_69f224dc84d0819081f1cb6f9127e6b1 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a9603b208190b3533ea2b441514c |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a915ead881909463ae46419c343e |
completed | May 3, 2026, 1:47 a.m. |
Created at: April 29, 2026, 9:11 p.m.