Triple
T11215647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Centrale |
E265431
|
entity |
| Predicate | employerReputation |
P83581
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Centrale, employerReputation, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: employerReputation Context triple: [Centrale, employerReputation, high]
-
A.
employerIn
Indicates that one entity serves as the employer of another within a specified context, such as a location, organization, or time period.
-
B.
employerSide
Indicates that the subject participates in or represents the employer’s position, interests, or perspective within an employment relationship or dispute.
-
C.
employerBrandingFor
Indicates that one entity develops, manages, or represents the employer brand or employer reputation on behalf of another entity.
-
D.
commercialReputation
chosen
Indicates the perceived standing or esteem of an entity in a commercial or business context, based on others’ experiences, opinions, or evaluations.
-
E.
employerFocus
Indicates that an employer directs particular attention, resources, or priority toward a specific subject, group, or area.
- 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_69d6aac59460819089b9848b27f57848 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8e8eef48190932a85784ce15c86 |
completed | April 9, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69d75cfbbb188190861efd5d94fe27da |
completed | April 9, 2026, 8:02 a.m. |
Created at: April 8, 2026, 9:30 p.m.