Triple
T23896986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alloy Entertainment |
E600930
|
entity |
| Predicate | basedOnManyProjects |
P153980
|
FINISHED |
| Object | young adult novels |
—
|
LITERAL FINISHED |
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: young adult novels | Statement: [Alloy Entertainment, basedOnManyProjects, young adult novels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnManyProjects Context triple: [Alloy Entertainment, basedOnManyProjects, young adult novels]
-
A.
hasProject
Indicates that an entity is associated with or responsible for a particular project.
-
B.
projectsOn
Indicates that one entity casts, directs, or extends itself onto the surface, area, or domain of another entity.
-
C.
hasProjectIn
Indicates that an entity is involved with or associated with a project that takes place within a specified location or context.
-
D.
basedOnPoliticalProjectOf
Indicates that something is founded upon, derived from, or guided by a particular political project, agenda, or program.
-
E.
hasPlannedProjects
Indicates that an entity is associated with projects that are intended or scheduled to be carried out in the future.
- 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_69e295341ac0819080647f2908af793c |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cdda39448190bdefa953e0558583 |
completed | April 29, 2026, 9:22 a.m. |
| PD | Predicate disambiguation | batch_69f1614e24b48190a1c8fb5b7c75ee0f |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f167dca3608190ace9d2eef56b2af6 |
completed | April 29, 2026, 2:07 a.m. |
Created at: April 17, 2026, 8:25 p.m.