Triple
T29045190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Lady of Aggieland |
E735114
|
entity |
| Predicate | hasTypicalBreed |
P193935
|
FINISHED |
| Object | Rough Collie |
—
|
NE NERFINISHED |
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: Rough Collie | Statement: [First Lady of Aggieland, hasTypicalBreed, Rough Collie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalBreed Context triple: [First Lady of Aggieland, hasTypicalBreed, Rough Collie]
-
A.
isRecognizedAsBreed
Indicates that an entity is officially acknowledged or accepted as a distinct breed within a particular classification or standard.
-
B.
sameBreedAs
Indicates that two entities belong to the same breed or variety within a species.
-
C.
breed
Indicates that an organism reproduces to generate offspring, typically with another organism of the same species.
-
D.
isHeritageBreed
Indicates that an animal breed belongs to a traditional, historically established lineage recognized for its cultural, genetic, or agricultural heritage.
-
E.
hasVarietyWithinBreed
Indicates that within a given breed, there exist distinct varieties or subtypes that are recognized as variations of that same breed.
- F. None of above. chosen
Provenance (4 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_69f077e64b88819094d37bdbca8191b3 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fd5bf69acc819092a01e4259785dc3 |
completed | May 8, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69fd59b3f4ac8190a7f9dd3142da6e09 |
completed | May 8, 2026, 3:34 a.m. |
| PDg | Predicate description generation | batch_69fd5bf49288819098a12202411cba4f |
completed | May 8, 2026, 3:43 a.m. |
Created at: April 28, 2026, 10:04 a.m.