Triple
T35134194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Starck Network |
E1014523
|
entity |
| Predicate | managesProjectsFor |
P127594
|
FINISHED |
| Object | Philippe Starck |
—
|
NE NERFINISHED |
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: Philippe Starck | Statement: [Starck Network, managesProjectsFor, Philippe Starck]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managesProjectsFor Context triple: [Starck Network, managesProjectsFor, Philippe Starck]
-
A.
overseesProject
Indicates that one entity has responsibility for supervising, managing, or directing the progress and execution of a project involving another entity.
-
B.
managingFor
chosen
Indicates that one entity is responsible for directing, supervising, or overseeing activities, resources, or operations on behalf of another entity.
-
C.
basedOnManyProjects
Indicates that something is derived from, influenced by, or constructed using multiple underlying projects.
-
D.
byProjectOf
Indicates that something is created, produced, or carried out by a specific project or initiative.
-
E.
projectsOn
Indicates that one entity casts, directs, or extends itself onto the surface, area, or domain 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_69f76dd9c1848190af70d4882a2c1ad7 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
Created at: May 3, 2026, 4:02 p.m.