Triple
T16317881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Top of the Heap |
E396217
|
entity |
| Predicate | featuresFamilyRelationship |
P89441
|
FINISHED |
| Object | father and 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: father and son | Statement: [Top of the Heap, featuresFamilyRelationship, father and son]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresFamilyRelationship Context triple: [Top of the Heap, featuresFamilyRelationship, father and son]
-
A.
familyConnectionTo
chosen
Indicates a familial relationship or bond that exists between two entities, such as by blood, marriage, or adoption.
-
B.
familyOf
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
-
C.
familyRelationNote
Indicates a descriptive note or annotation that provides additional context or clarification about a specified family relationship between entities.
-
D.
featuresFamilyFrom
Indicates that something includes or presents a family originating from or associated with a specified source.
-
E.
playerRelations
Indicates the nature or status of the relationship between players, such as alliances, rivalries, or other interpersonal dynamics.
- 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_69d87f255b788190a400eba031dd85d8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e296b31b988190bb1fde36dae11bbd |
completed | April 17, 2026, 8:23 p.m. |
| PD | Predicate disambiguation | batch_69e219fc72c881909d452274e7af8238 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:06 a.m.