Triple
T13571354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Century 21 |
E324168
|
entity |
| Predicate | operatesInIndustrySegment |
P1670
|
FINISHED |
| Object | residential real estate |
—
|
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: residential real estate | Statement: [Century 21, operatesInIndustrySegment, residential real estate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesInIndustrySegment Context triple: [Century 21, operatesInIndustrySegment, residential real estate]
-
A.
operatesInSegment
chosen
Indicates that an entity conducts its activities or provides its services within a specified market or operational segment.
-
B.
containsIndustry
Indicates that one entity includes or encompasses a particular industry within its scope, structure, or operations.
-
C.
sectorOfOperation
Indicates the industry, domain, or field within which an entity conducts its primary activities or operations.
-
D.
isPartOfIndustry
Indicates that one entity belongs to, operates within, or is categorized under a particular industry sector.
-
E.
operatorIndustry
Indicates that an operator (such as a company or organization) is engaged in or associated with a particular industry sector.
- 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.