Triple
T27936330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valiant & Valiant |
E700621
|
entity |
| Predicate | hasPrimaryDetective |
P175876
|
FINISHED |
| Object | Eddie Valiant |
—
|
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: Eddie Valiant | Statement: [Valiant & Valiant, hasPrimaryDetective, Eddie Valiant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryDetective Context triple: [Valiant & Valiant, hasPrimaryDetective, Eddie Valiant]
-
A.
hasClericalDetective
Indicates that an entity includes or is associated with a detective who is also a member of the clergy.
-
B.
hasFictionalDetective
Indicates that one entity (typically a work or series) features or includes a fictional detective character as part of its content.
-
C.
detectiveType
Indicates that one entity is classified as a particular type or category of detective in relation to another entity.
-
D.
hasSleuth
chosen
Indicates that an entity is associated with or employs a sleuth (detective) responsible for investigating on its behalf.
-
E.
detectiveMethod
Indicates that one entity uses or is associated with a particular method or technique in the context of detective work or investigation.
- 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_69ef6a5028108190a14696d9821dde49 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fe7eb4b8348190bb19d35766189ed4 |
completed | May 9, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69fe7c35d2148190ab952e54feda1e76 |
completed | May 9, 2026, 12:13 a.m. |
Created at: April 27, 2026, 7:13 p.m.