Triple
T22861446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bezons |
E566931
|
entity |
| Predicate | hostsSector |
P78681
|
FINISHED |
| Object | information technology companies |
—
|
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: information technology companies | Statement: [Bezons, hostsSector, information technology companies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostsSector Context triple: [Bezons, hostsSector, information technology companies]
-
A.
hostsCompany
Indicates that one entity provides space, infrastructure, or support for a company to operate, be located, or hold activities.
-
B.
targetsSector
Indicates that an entity is directed toward, focused on, or intended to affect a particular economic or industry sector.
-
C.
hostsPartOf
Indicates that one entity serves as the hosting environment or container for a specific part or component of another entity.
-
D.
ownerSector
Indicates the sector or industry category to which the owner of an entity belongs.
-
E.
sectorBase
chosen
Indicates that one entity serves as the primary base or foundational location for operations within a particular sector of another entity.
- 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_69e24589083081908d5694c4fdc80086 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17efcc1308190a95d10e431295ca2 |
completed | April 29, 2026, 3:46 a.m. |
| PD | Predicate disambiguation | batch_69eed2d507c08190895ed971af0fc755 |
completed | April 27, 2026, 3:07 a.m. |
Created at: April 17, 2026, 3:37 p.m.