Triple
T3075200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rooney family |
E64118
|
entity |
| Predicate | generationalOwnership |
P27004
|
FINISHED |
| Object | third generation |
—
|
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: third generation | Statement: [Rooney family, generationalOwnership, third generation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: generationalOwnership Context triple: [Rooney family, generationalOwnership, third generation]
-
A.
multiGenerationControl
chosen
Indicates a relationship where one entity exercises control or influence over multiple successive generations of another entity or group.
-
B.
ownershipType
Indicates the specific nature or category of the ownership relationship that one entity holds over another.
-
C.
ownershipCharacteristic
Indicates that one entity possesses a particular quality, attribute, or condition specifically in its role as an owner of another entity.
-
D.
acquiredByCurrentOwner
Indicates that the entity was obtained or purchased by its present owner, rather than being originally created or owned by them.
-
E.
ownedBy
Indicates that one entity possesses legal or rightful ownership of another entity.
- 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_69ad857a8aec8190bfdfd9c14554ac5a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada150d8e08190bde5f68e800e8feb |
completed | March 8, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69ad9625b30c819099ef9349c91d7b25 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:02 p.m.