Triple
T29895479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TDR Capital |
E759265
|
entity |
| Predicate | exitStrategies |
P140954
|
FINISHED |
| Object | Trade sales |
—
|
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: Trade sales | Statement: [TDR Capital, exitStrategies, Trade sales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exitStrategies Context triple: [TDR Capital, exitStrategies, Trade sales]
-
A.
exitTo
Indicates that one location or entity serves as a passage or route leading directly to another location or entity.
-
B.
exitRoutes
chosen
Indicates that there are designated paths or ways for entities to leave or move out from a particular place or situation.
-
C.
marketExit
Indicates that an entity ceases operating, selling, or competing in a particular market or geographic/segment context.
-
D.
terminationMechanism
Indicates the process or method by which an ongoing state, activity, or relationship is brought to an end.
-
E.
escapeStatus
Indicates whether an entity has escaped, is in the process of escaping, or has not escaped from a given situation or confinement.
- 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_69f2245f1cf88190978c70d1a1d2cb73 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6772a62a08190a8f625b73e261ba9 |
completed | May 2, 2026, 10:14 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:04 p.m.