Triple
T20860245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beda Fell |
E513595
|
entity |
| Predicate | hasRelativeCharacter |
P71486
|
FINISHED |
| Object | modest height |
—
|
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: modest height | Statement: [Beda Fell, hasRelativeCharacter, modest height]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelativeCharacter Context triple: [Beda Fell, hasRelativeCharacter, modest height]
-
A.
hasRelativeLocation
Indicates that one entity is positioned in space in relation to another entity’s location.
-
B.
hasRelativeRole
Indicates that one entity holds a familial or kinship-based role in relation to another entity.
-
C.
containsCharacter
Indicates that one entity includes a specific character as part of its content or composition.
-
D.
isRelatively
chosen
Indicates that one entity is being described, measured, or evaluated in relation to another entity or reference point, rather than in absolute terms.
-
E.
hasSpecialCharacter
Indicates that a given entity (such as a string or identifier) contains at least one non-alphanumeric special character.
- 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_69e0b4f5b01081909452f654d2fc3f50 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c3aba3d0819093431f38f0095a71 |
completed | April 21, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a593f481908beb457c29f1ce73 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:44 p.m.