Triple
T27234278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Castafiore Emerald |
E682232
|
entity |
| Predicate | hasScriptBy |
P173216
|
FINISHED |
| Object | Hergé |
—
|
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: Hergé | Statement: [The Castafiore Emerald, hasScriptBy, Hergé]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScriptBy Context triple: [The Castafiore Emerald, hasScriptBy, Hergé]
-
A.
containsScript
Indicates that one entity includes or embeds the script of another entity within it.
-
B.
hasScriptTool
Indicates that an entity uses, is associated with, or is supported by a particular scripting tool or scripting environment.
-
C.
hasScriptStatus
Indicates that an entity has a particular script-related state or condition, such as whether a script is present, active, or in a given status.
-
D.
usesScriptFor
Indicates that one entity employs or relies on a particular script or writing system for its representation, communication, or operation.
-
E.
hasNotableScript
Indicates that an entity is associated with a script (such as a writing system or screenplay) that is considered notable or significant.
- 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_69eefacdad7881908b7bca61c90a1a1e |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6b342499c8190b85009a3f0f179e4 |
completed | May 3, 2026, 2:30 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b2a31e008190aacef03c2ebe5787 |
completed | May 3, 2026, 2:27 a.m. |
Created at: April 27, 2026, 9:47 a.m.