Triple
T36156260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Show |
E1045740
|
entity |
| Predicate | judgingStandard |
P82415
|
FINISHED |
| Object | breed standards |
—
|
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: breed standards | Statement: [World Show, judgingStandard, breed standards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: judgingStandard Context triple: [World Show, judgingStandard, breed standards]
-
A.
judgedBy
Indicates that one entity evaluates, assesses, or forms an opinion about another entity, often in an official or critical capacity.
-
B.
judgedAs
Indicates that one entity evaluates or forms an opinion about another entity according to some criteria or standard.
-
C.
judgedOn
chosen
Indicates that an entity is evaluated or assessed based on a specified criterion, standard, or aspect.
-
D.
normativelyJudgedAs
Indicates that one entity evaluates another according to normative standards, assigning a judgment of what ought to be approved, disapproved, right, or wrong.
-
E.
judgeQualification
Indicates that one entity evaluates and determines whether another entity meets certain standards, criteria, or requirements.
- 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_69f76e38903c8190a52887620f90aabe |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:08 p.m.