Triple
T18642718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fed |
E455728
|
entity |
| Predicate | bearerHandedness |
P132842
|
FINISHED |
| Object | right-handed |
—
|
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: right-handed | Statement: [Fed, bearerHandedness, right-handed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bearerHandedness Context triple: [Fed, bearerHandedness, right-handed]
-
A.
bearerAlignedWith
Indicates that the bearer’s position, orientation, or stance is arranged in line with, or matches, that of another specified reference.
-
B.
bearer
Indicates that one entity carries, holds, or possesses another entity, often as the current holder of a right, document, or object.
-
C.
bearerStance
Indicates the attitude, position, or viewpoint that the bearer holds toward a referenced subject or issue.
-
D.
bearerField
Indicates that one entity serves as the bearer or holder of a specific field, attribute, or property associated with another entity.
-
E.
bearerFounded
Indicates that the bearer (such as a person or organization) is the one who established or created the associated entity (such as a company, institution, or project).
- 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_69d8d38ea1e88190997e9b231190ba6f |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54fcd6da081908030b052727f2c2f |
completed | April 19, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69e478d85864819093cbad5ed9b54878 |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484121cd48190bf583b4c94636a30 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:47 a.m.