Triple
T36253493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Republic Industries |
E891863
|
entity |
| Predicate | componentBusinessSpunOffAs |
P7736
|
FINISHED |
| Object | AutoNation |
—
|
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: AutoNation | Statement: [Republic Industries, componentBusinessSpunOffAs, AutoNation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: componentBusinessSpunOffAs Context triple: [Republic Industries, componentBusinessSpunOffAs, AutoNation]
-
A.
associatedCompanyHasSpinOff
Indicates that a company is related to another company that has been created as its spin-off.
-
B.
spunOffOrganizationIn
Indicates that one organization was created as a spin-off from another organization within a specified location or context.
-
C.
spinOff
chosen
Indicates that a new entity is created by separating or divesting part of an existing entity, forming an independent offshoot derived from the original.
-
D.
associatedCompanySpinOffYear
Indicates the year in which a related or associated company was spun off from its original parent organization.
-
E.
corporateSeparation
Indicates a formal division or split of a corporate entity into distinct, separately organized business units or companies.
- 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_69f76e4599108190811532e707d6bc2c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fdd07a34c08190982b8c61c2775cf6 |
completed | May 8, 2026, noon |
| PD | Predicate disambiguation | batch_69fdbd25c7908190b72fca8de7ce503f |
completed | May 8, 2026, 10:38 a.m. |
Created at: May 3, 2026, 4:09 p.m.