Triple
T35967753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camp Half-Blood |
E1040191
|
entity |
| Predicate | hasActivitiesDirector |
P75904
|
FINISHED |
| Object | Chiron |
—
|
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: Chiron | Statement: [Camp Half-Blood, hasActivitiesDirector, Chiron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasActivitiesDirector Context triple: [Camp Half-Blood, hasActivitiesDirector, Chiron]
-
A.
hasHumanActivities
Indicates that certain human actions, behaviors, or practices are present, performed, or associated with a given entity.
-
B.
hasDirectorOfWork
Indicates that an entity has a specific person or organization serving as the director responsible for overseeing its work or project.
-
C.
hasActivityIn
Indicates that an entity engages in or performs a particular activity within a specified context, location, or domain.
-
D.
hasPrimaryDirector
chosen
Indicates that an entity has a specific person or organization serving as its main or lead director.
-
E.
hasDirectorInKeyWork
Indicates that a director is associated with a key or primary work of an entity (such as a film, series, or major production).
- 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_69f76e26b21081909fd9ffb3aff6c77a |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:07 p.m.