Triple
T26870558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fairfield Sentry |
E676598
|
entity |
| Predicate | wasKeyVehicleIn |
P161546
|
FINISHED |
| Object | global distribution of Madoff-related products |
—
|
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: global distribution of Madoff-related products | Statement: [Fairfield Sentry, wasKeyVehicleIn, global distribution of Madoff-related products]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasKeyVehicleIn Context triple: [Fairfield Sentry, wasKeyVehicleIn, global distribution of Madoff-related products]
-
A.
usedAsVehicleFor
Indicates that one entity functions as a means of transportation or conveyance for another entity.
-
B.
hasVehicle
Indicates that one entity possesses, owns, or is assigned a vehicle.
-
C.
hasVehicularUse
Indicates that something is used for, intended for, or associated with operation by vehicles or vehicular traffic.
-
D.
hasPrimaryVehicularAccessTo
Indicates that one location or entity serves as the main route or means by which vehicles can reach or enter another location or entity.
-
E.
vehicleUsed
Indicates that a particular vehicle is utilized or employed in performing an action, event, or activity.
- 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_69eee9ba94bc8190b44c5d4397d04ecd |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61e9b57bc8190a262eb0203f9dd3f |
completed | May 2, 2026, 3:56 p.m. |
| PD | Predicate disambiguation | batch_69f611ad2eb48190ac1ed0090f13f7a9 |
completed | May 2, 2026, 3:01 p.m. |
| PDg | Predicate description generation | batch_69f6142a0b988190b404d078f73c3cb9 |
completed | May 2, 2026, 3:11 p.m. |
Created at: April 27, 2026, 5:32 a.m.