Triple
T28206196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PoP! |
E717028
|
entity |
| Predicate | createdByFilmDirector |
P146707
|
FINISHED |
| Object | Marc Lawrence |
—
|
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: Marc Lawrence | Statement: [PoP!, createdByFilmDirector, Marc Lawrence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdByFilmDirector Context triple: [PoP!, createdByFilmDirector, Marc Lawrence]
-
A.
hasDirectorCreator
chosen
Indicates that an entity has a person or organization who directed or created it (e.g., a film’s director or a work’s creator).
-
B.
usedByDirector
Indicates that something (such as a resource, tool, or method) is utilized or employed by a director in their work or activities.
-
C.
basedOnFilmDirector
Indicates that something is derived from, adapted from, or otherwise conceptually grounded in the work or role of a particular film director.
-
D.
workedWithDirector
Indicates that one entity has collaborated professionally with a director on a project or production.
-
E.
hasCreatorForFilmVersion
Indicates that an entity is the creator (e.g., director, primary filmmaker) responsible for a particular film version of a work.
- 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_69efd6b826908190857e6e7dad74ed93 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: April 27, 2026, 10:35 p.m.