Triple
T17906491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Eds |
E447714
|
entity |
| Predicate | targetOfSchemes |
P860
|
FINISHED |
| Object | the other kids in the cul-de-sac |
—
|
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: the other kids in the cul-de-sac | Statement: [the Eds, targetOfSchemes, the other kids in the cul-de-sac]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetOfSchemes Context triple: [the Eds, targetOfSchemes, the other kids in the cul-de-sac]
-
A.
targetsUseCase
Indicates that one entity is aimed at or designed to address a particular use case associated with another entity.
-
B.
targetsProvidedBy
Indicates that one entity supplies or makes available specific targets for another entity to use or act upon.
-
C.
targetsSystems
Indicates that an entity is directed at, attacks, or is intended to affect specific systems.
-
D.
intendedTargets
Indicates that an action, message, or object is specifically directed toward or meant to affect particular target entities.
-
E.
target
chosen
Indicates that one entity is the intended object, goal, or focus of another entity’s action or attention.
- 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_69d8b9f6d394819082a6d69fd1e23d2f |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49e9c7f54819088c6d2ce7bbea073 |
completed | April 19, 2026, 9:21 a.m. |
| PD | Predicate disambiguation | batch_69e3d8ec2f6881909d7f54b878cbed37 |
completed | April 18, 2026, 7:18 p.m. |
Created at: April 10, 2026, 10:19 a.m.