Triple
T9177218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buff Orpington |
E220230
|
entity |
| Predicate | hasStatusInAPA |
P15010
|
FINISHED |
| Object | standard breed |
—
|
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: standard breed | Statement: [Buff Orpington, hasStatusInAPA, standard breed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStatusInAPA Context triple: [Buff Orpington, hasStatusInAPA, standard breed]
-
A.
hasStatusIn
chosen
Indicates that an entity holds or is assigned a particular status within a specified context, scope, or system.
-
B.
hasStatusLabel
Indicates that an entity is associated with a specific status expressed as a human-readable label.
-
C.
hasActivityStatus
Indicates the current state or condition of an activity, such as whether it is planned, ongoing, completed, or cancelled.
-
D.
hasProductionStatus
Indicates the current stage or condition of an entity’s production process (e.g., planned, in progress, completed, or discontinued).
-
E.
hasPolicyStatus
Indicates that an entity is associated with a policy and specifies the current status or state of that policy.
- 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_69ca83e589948190ac9907819db11ddf |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccbfa60c3c8190b6335b9067de5b72 |
completed | April 1, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_69cc660761d88190ab6134b43b376964 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:23 p.m.