Triple
T19872270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kangaroo Jack |
E477546
|
entity |
| Predicate | includesCGICharacters |
P98529
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Kangaroo Jack, includesCGICharacters, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesCGICharacters Context triple: [Kangaroo Jack, includesCGICharacters, true]
-
A.
usesCGI
chosen
Indicates that one entity employs computer-generated imagery (CGI) in the creation, enhancement, or presentation of another entity.
-
B.
usesCharactersAs
Indicates that one entity employs or incorporates specific characters (such as letters, symbols, or glyphs) from another entity for its representation or functioning.
-
C.
hasSpecialCharacter
Indicates that a given entity (such as a string or identifier) contains at least one non-alphanumeric special character.
-
D.
hasLanguageCharacter
Indicates that an entity uses, contains, or is associated with a specific written or symbolic character from a language.
-
E.
hasNoConventionalCharacters
Indicates that the entity contains no standard alphanumeric or commonly used written characters.
- 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_69d8e51e7d948190aedbcd6c30361c39 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e658d826f88190be04188997952d1b |
completed | April 20, 2026, 4:48 p.m. |
| PD | Predicate disambiguation | batch_69e537e8c4e481909fe95d795b4864e7 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:51 p.m.