Triple
T32040167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Petty Enterprises |
E818199
|
entity |
| Predicate | familyTeamOf |
P162104
|
FINISHED |
| Object | Petty family |
—
|
NE NERFINISHED |
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: Petty family | Statement: [Petty Enterprises, familyTeamOf, Petty family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyTeamOf Context triple: [Petty Enterprises, familyTeamOf, Petty family]
-
A.
fatherTeam
Indicates that one team serves as the originating, parent, or predecessor team from which another team is derived or formed.
-
B.
familyOf
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
-
C.
ownerFamily
Indicates that a family has ownership or proprietary rights over a particular entity or resource.
-
D.
familyProjectOf
chosen
Indicates that one entity is a project that is created, owned, or carried out by a particular family.
-
E.
familyGroup
Indicates that multiple entities are related to each other as members of the same family unit or household.
- 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_69f348fbc8148190b3c0f95d4772b153 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 1, 2026, 12:19 a.m.