Triple
T34804005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arabian Construction Company |
E1003298
|
entity |
| Predicate | projectProfile |
P182296
|
FINISHED |
| Object | high-profile |
—
|
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-profile | Statement: [Arabian Construction Company, projectProfile, high-profile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: projectProfile Context triple: [Arabian Construction Company, projectProfile, high-profile]
-
A.
profile
Indicates that one entity creates, presents, or analyzes a detailed description or representation of another entity’s characteristics or behavior.
-
B.
personelProfili
Indicates a relationship that associates an entity with a personnel profile, capturing information or attributes specific to that personnel.
-
C.
projectModel
Indicates a relationship where one entity serves as a model, template, or representation for a project or projected outcome involving another entity.
-
D.
project
Indicates that an entity plans, organizes, or carries out a structured effort or initiative aimed at achieving a specific goal or outcome.
-
E.
profileDirectory
Indicates the directory path where a user's or application's profile data is stored or managed.
- F. None of above. chosen
Provenance (4 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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f7886b27f08190ab4580f949222c93 |
completed | May 3, 2026, 5:39 p.m. |
Created at: May 3, 2026, 3:59 p.m.