Triple
T13571375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Century 21 |
E324168
|
entity |
| Predicate | officeOwnershipModel |
P21682
|
FINISHED |
| Object | independently owned and operated |
—
|
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: independently owned and operated | Statement: [Century 21, officeOwnershipModel, independently owned and operated]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeOwnershipModel Context triple: [Century 21, officeOwnershipModel, independently owned and operated]
-
A.
ownershipType
Indicates the specific nature or category of the ownership relationship that one entity holds over another.
-
B.
ownershipModel
chosen
Indicates the type or structure of ownership relationship that governs how control, rights, or shares are held between entities.
-
C.
ownsOrLeases
Indicates that one entity has legal rights to use or control another entity either through ownership or through a lease agreement.
-
D.
ownsService
Indicates that one entity has ownership or control over a particular service.
-
E.
ownedIn
Indicates that one entity possesses or holds legal or recognized ownership of another entity within a specific context, domain, or scope.
- 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_69d80769100c819099111274614f5ed2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb00f5b8881908617f42d227ed137 |
completed | April 12, 2026, 2:45 p.m. |
| PD | Predicate disambiguation | batch_69dbae161a0481909f9d3f40ca4e0ac5 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:48 p.m.