Triple
T37805128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beast (The Wolf Among Us) |
E942479
|
entity |
| Predicate | relationshipTypeWith Bigby Wolf |
P96394
|
FINISHED |
| Object | tense |
—
|
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: tense | Statement: [Beast (The Wolf Among Us), relationshipTypeWith Bigby Wolf, tense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipTypeWith Bigby Wolf Context triple: [Beast (The Wolf Among Us), relationshipTypeWith Bigby Wolf, tense]
-
A.
relationshipToCreature
chosen
Indicates a specified type of relational connection that one entity has toward a particular creature.
-
B.
relationshipToWolverine
Indicates the specific interpersonal or familial connection an entity has with Wolverine.
-
C.
relationshipToFelix
Indicates the specific type of relationship or connection that an entity has with Felix.
-
D.
opusRelationship
Indicates a relationship between creative works (opuses), such as versions, adaptations, or parts within a larger compositional whole.
-
E.
bondedWithSpecies
Indicates a relationship where an entity has formed a close, enduring bond or attachment with a particular species.
- 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_69f76ee8104c8190ab17133ccd8f86e6 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:19 p.m.