Triple
T31862572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strawberries Oceans Ships Forest |
E813370
|
entity |
| Predicate | hasSideProjectName |
P22083
|
FINISHED |
| Object | The Fireman |
—
|
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 Fireman | Statement: [Strawberries Oceans Ships Forest, hasSideProjectName, The Fireman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSideProjectName Context triple: [Strawberries Oceans Ships Forest, hasSideProjectName, The Fireman]
-
A.
formedAsSideProjectOf
Indicates that something was created or developed as a secondary or unofficial project alongside another primary project or activity.
-
B.
sideProjectOf
chosen
Indicates that one activity, endeavor, or project is a secondary or supplementary effort carried out alongside a primary or main project.
-
C.
hasProject
Indicates that an entity is associated with or responsible for a particular project.
-
D.
hasProjectIn
Indicates that an entity is involved with or associated with a project that takes place within a specified location or context.
-
E.
hasNearbyProject
Indicates that one entity has a project located within a close or specified proximity to another entity or reference point.
- 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_69f348ebf32881908d9439646933dc76 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
Created at: April 30, 2026, 11:53 p.m.