Triple
T38402662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Night of Thunder |
E900941
|
entity |
| Predicate | hasBreedingStatus |
P75523
|
FINISHED |
| Object | active stallion |
—
|
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: active stallion | Statement: [Night of Thunder, hasBreedingStatus, active stallion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBreedingStatus Context triple: [Night of Thunder, hasBreedingStatus, active stallion]
-
A.
breedingStatus
chosen
Indicates the reproductive condition or phase an entity is currently in, such as whether it is capable of, engaged in, or excluded from breeding.
-
B.
hasBreedingCode
Indicates that an entity is associated with a specific code representing its breeding status, behavior, or category.
-
C.
hasBreedingFocus
Indicates that an entity is the primary target or subject of another entity’s breeding efforts or breeding program.
-
D.
breedingType
Indicates the method or strategy by which organisms reproduce or are bred.
-
E.
hasBreedingMechanicIntroduced
Indicates that a breeding-related game mechanic has been introduced or made available within the system or context.
- 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_69f76e6071a081909eea7a670d21420c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
Created at: May 3, 2026, 4:31 p.m.