Triple
T13431327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green Family Holdings |
E313616
|
entity |
| Predicate | controlsAssetsFor |
P109899
|
FINISHED |
| Object | Green family |
—
|
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: Green family | Statement: [Green Family Holdings, controlsAssetsFor, Green family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlsAssetsFor Context triple: [Green Family Holdings, controlsAssetsFor, Green family]
-
A.
controlsAccessTo
Indicates that one entity regulates, manages, or determines the ability of another entity to reach, use, or interact with a resource, location, or service.
-
B.
protectedAsset
Indicates that one entity serves as a safeguarded or defended resource in relation to another entity.
-
C.
mainAssetManaged
Indicates that one entity is responsible for managing another entity that serves as the primary or main asset.
-
D.
controlsAccessBetween
Indicates that one entity regulates, manages, or restricts the ability of another entity to interact or communicate with a third entity or resource.
-
E.
controlsWith
Indicates that one entity exercises authority, direction, or regulatory power over another entity through specific means or mechanisms.
- 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_69d806ad0c44819088833ae1ec9e9690 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaed41a5481908800033303224adb |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03926188190ab3948d1f5d3941f |
completed | April 11, 2026, 1:13 a.m. |
| PDg | Predicate description generation | batch_69dadcce5a808190847f2a7833b67a5a |
completed | April 11, 2026, 11:44 p.m. |
Created at: April 9, 2026, 9:40 p.m.