Triple
T36253146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chris Gaines |
E891854
|
entity |
| Predicate | projectPlannedFor |
P186004
|
FINISHED |
| Object | The Lamb |
—
|
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: The Lamb | Statement: [Chris Gaines, projectPlannedFor, The Lamb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: projectPlannedFor Context triple: [Chris Gaines, projectPlannedFor, The Lamb]
-
A.
plannedIn
Indicates that an event, activity, or process is scheduled or arranged to occur within a specific context, timeframe, or plan.
-
B.
plannedWith
Indicates that an entity created or arranged a plan in collaboration or coordination with another entity.
-
C.
plannedAt
Indicates that an event, action, or activity is scheduled or intended to occur at a specific time or date.
-
D.
platformPlanned
Indicates that a platform is intended or scheduled to be created, implemented, or made available in the future.
-
E.
isPlannedThrough
Indicates that something is intended to be achieved, organized, or carried out by means of a specified plan, method, or intermediary process.
- 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_69f76e4599108190811532e707d6bc2c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c83f5960819089610ed39c839678 |
completed | May 3, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
| PDg | Predicate description generation | batch_69f7c776b4088190bef550c869da530d |
completed | May 3, 2026, 10:08 p.m. |
Created at: May 3, 2026, 4:09 p.m.