Triple
T17662421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unbridled |
E440284
|
entity |
| Predicate | becameSire |
P128450
|
FINISHED |
| Object | early 1990s |
—
|
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: early 1990s | Statement: [Unbridled, becameSire, early 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: becameSire Context triple: [Unbridled, becameSire, early 1990s]
-
A.
turnedIntoVampireIn
Indicates that an entity became a vampire at or within a specified place or context.
-
B.
turnedIntoWerewolfBy
Indicates that one entity was transformed into a werewolf as a result of the actions or influence of another entity.
-
C.
becomesImmortalIn
Indicates that an entity transitions into a state of immortality within a specified context, time, or medium.
-
D.
crownTransformedInto
Indicates that a crown undergoes a change of state or form, resulting in it becoming a different specified object or condition.
-
E.
damsire
Indicates that one entity is the maternal grandfather (sire of the dam) of another, typically in an animal’s pedigree.
- 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_69d8b9e87e18819087104a44dc4dc5b1 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e46ea73c90819087a23a7b6171f581 |
completed | April 19, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69e3cde007d8819090dd92eea9f022cc |
completed | April 18, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69e3cfaac2b881909e1140339eb1a0dd |
completed | April 18, 2026, 6:38 p.m. |
Created at: April 10, 2026, 9:48 a.m.