Triple
T31233974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prized Possessions |
E796363
|
entity |
| Predicate | mainTopics |
P26448
|
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: [Prized Possessions, mainTopics, family relationships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainTopics Context triple: [Prized Possessions, mainTopics, family relationships]
-
A.
coveredTopics
Indicates that certain subjects or themes have been addressed or included within a discussion, document, or activity.
-
B.
primaryTopicOf
Indicates that a given subject is the main or central topic described by another resource (such as a document, page, or record).
-
C.
principleTopic
Indicates that one entity serves as the main or primary subject, theme, or focus of another entity.
-
D.
featuresTopic
chosen
Indicates that something (such as a work, event, or item) prominently includes, focuses on, or is organized around a particular topic.
-
E.
subjectCategories
Indicates that an entity is associated with one or more subject-based categories or classifications.
- 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_69f224db69ac81909a370adad6a7ac7c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
Created at: April 29, 2026, 9:10 p.m.