Triple
T23699908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ford Model 48 |
E585562
|
entity |
| Predicate | successInMarket |
P138380
|
FINISHED |
| Object | popular in North America |
—
|
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: popular in North America | Statement: [Ford Model 48, successInMarket, popular in North America]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successInMarket Context triple: [Ford Model 48, successInMarket, popular in North America]
-
A.
successorInMarket
Indicates that one entity has taken over or followed another in serving the same market or customer base.
-
B.
successMetric
Indicates the specific criterion or measure used to evaluate whether an action, process, or relationship has achieved its intended success.
-
C.
commercialSuccessIn
chosen
Indicates that something has achieved notable commercial success within a specified market, region, or domain.
-
D.
continuedCommercialSuccessFor
Indicates that an entity maintains its strong commercial performance or profitability over an extended period of time.
-
E.
successInOffice
Indicates that an individual has achieved a positive or effective performance outcome while holding a particular office or position.
- 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_69e24904bd508190abfcb74855de2918 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b681a93c8190b8dab12e7f0aa6fd |
completed | April 29, 2026, 7:42 a.m. |
| PD | Predicate disambiguation | batch_69f155d5265881908e43a9696b6a6d0f |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 6:53 p.m.