Triple
T32058638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexander Pierce |
E818686
|
entity |
| Predicate | controlsProject |
P11213
|
FINISHED |
| Object | Project Insight |
—
|
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: Project Insight | Statement: [Alexander Pierce, controlsProject, Project Insight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlsProject Context triple: [Alexander Pierce, controlsProject, Project Insight]
-
A.
overseesProject
chosen
Indicates that one entity has responsibility for supervising, managing, or directing the progress and execution of a project involving another entity.
-
B.
centralProject
Indicates that one project serves as the primary or core project around which other related projects or activities are organized.
-
C.
exportControl
Indicates that an entity is subject to rules or restrictions governing the transfer or export of goods, services, or information across borders.
-
D.
exportProject
Indicates initiating the transfer or packaging of a project’s data or configuration from one system, format, or environment to another.
-
E.
controlStand
Indicates that one entity manages, directs, or regulates the operation or behavior of another entity or system.
- 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_69f348fdacec8190b9f74375ca3b2094 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fdf5d05cc481909ec9e1b1f0784279 |
completed | May 8, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69fdf0cdd6948190838864ab3120dfa6 |
completed | May 8, 2026, 2:18 p.m. |
Created at: May 1, 2026, 12:21 a.m.