Triple
T16863581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Digital Real Estate Services |
E409980
|
entity |
| Predicate | competitorType |
P2440
|
FINISHED |
| Object | online real estate portals |
—
|
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: online real estate portals | Statement: [Digital Real Estate Services, competitorType, online real estate portals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competitorType Context triple: [Digital Real Estate Services, competitorType, online real estate portals]
-
A.
competitorOwner
Indicates that one entity owns or controls a business or asset that competes in the same market or domain as another entity’s business or asset.
-
B.
competitorCount
Indicates the number of competitors associated with a given entity or context.
-
C.
typeOfCompetition
chosen
Indicates the specific kind or category of competition in which an entity participates or is involved.
-
D.
competitionOf
Indicates a relationship where one entity is the competitive event, contest, or rivalry involving another entity.
-
E.
partnerInCompetition
Indicates that two or more entities are collaborating as partners or teammates within the same competitive event or context.
- 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_69d88395e6c88190b22730f335107c14 |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b505a390819097ec31cd210eca60 |
completed | April 18, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69e32b8cbb048190878a259cc5be960e |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:24 a.m.