Triple
T30537946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lincoln ActiveGlide |
E777198
|
entity |
| Predicate | marketingNameRegion |
P175374
|
FINISHED |
| Object | Lincoln vehicles in the United States |
—
|
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: Lincoln vehicles in the United States | Statement: [Lincoln ActiveGlide, marketingNameRegion, Lincoln vehicles in the United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marketingNameRegion Context triple: [Lincoln ActiveGlide, marketingNameRegion, Lincoln vehicles in the United States]
-
A.
marketRegion
Indicates the geographic or demographic area in which a product, service, or entity is actively marketed or targeted.
-
B.
catalogRegion
Indicates the geographic or organizational region associated with a given catalog or catalog entry.
-
C.
marketingNameOf
Indicates that one entity is the marketing or brand name used to promote or refer to another entity.
-
D.
campaignRegion
Indicates the geographic area or territory in which a campaign is conducted or targeted.
-
E.
hasMarketingRegion
Indicates that an entity is associated with or assigned to a specific marketing region for targeting, management, or analysis purposes.
- 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_69f2249d183c8190b79937c1768d2163 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6d1d916f881909575c2b22c416a5b |
completed | May 3, 2026, 4:40 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
| PDg | Predicate description generation | batch_69f6d0d331dc8190be5aa6bfc6365e67 |
completed | May 3, 2026, 4:36 a.m. |
Created at: April 29, 2026, 8:19 p.m.