Triple
T30264603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alamo Rent A Car |
E769600
|
entity |
| Predicate | isBrandAlongside |
P10460
|
FINISHED |
| Object | Enterprise Rent-A-Car |
—
|
NE NERFINISHED |
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: Enterprise Rent-A-Car | Statement: [Alamo Rent A Car, isBrandAlongside, Enterprise Rent-A-Car]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBrandAlongside Context triple: [Alamo Rent A Car, isBrandAlongside, Enterprise Rent-A-Car]
-
A.
isBrand
Indicates that one entity functions as the commercial brand or label associated with another entity.
-
B.
usesSameBrandFamilyAs
Indicates that two entities use products or services belonging to the same overarching brand family or brand portfolio.
-
C.
relatedBrand
chosen
Indicates a relationship where one brand is associated with, connected to, or otherwise related to another brand.
-
D.
hasBrandRole
Indicates that an entity holds a specific functional or organizational role in relation to a particular brand.
-
E.
hasCoBrand
Indicates that two brands are jointly associated or partnered in offering a product, service, or marketing initiative.
- 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_69f22484a5f48190b678cd607700bc82 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f680abfd708190ba353bf8c06d794a |
completed | May 2, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:42 p.m.