Triple
T17907233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kids Next Door |
E447732
|
entity |
| Predicate | recruitmentRule |
P4702
|
FINISHED |
| Object | only children allowed |
—
|
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: only children allowed | Statement: [Kids Next Door, recruitmentRule, only children allowed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recruitmentRule Context triple: [Kids Next Door, recruitmentRule, only children allowed]
-
A.
recruitmentPolicy
chosen
Indicates the rules, criteria, and procedures an organization follows when attracting, selecting, and hiring candidates.
-
B.
recruitmentBasis
Indicates the criteria, grounds, or conditions on which an entity is recruited or selected for a role or position.
-
C.
recruitmentRequirement
Indicates that a certain condition, qualification, or criterion must be satisfied for an entity to be eligible for recruitment or hiring.
-
D.
recruitmentBase
Indicates the foundational source, location, or context from which recruitment efforts or recruited entities originate.
-
E.
recruitmentFrom
Indicates that one entity recruits or sources members, employees, or participants from another entity.
- 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_69e49e9d458881909e35e1c7a6e85436 |
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.