Triple
T38590952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viera |
E932450
|
entity |
| Predicate | jobAffinity |
P87255
|
FINISHED |
| Object | archer-type jobs |
—
|
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: archer-type jobs | Statement: [Viera, jobAffinity, archer-type jobs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: jobAffinity Context triple: [Viera, jobAffinity, archer-type jobs]
-
A.
possibleAffinity
chosen
Indicates a potential or likely positive relationship, attraction, or compatibility between two entities, without asserting that it is confirmed or realized.
-
B.
associatedWithWorkforce
Indicates a relationship in which an entity is connected or related to a particular workforce, such as its members, activities, or management.
-
C.
partnerAffiliation
Indicates that two entities are formally associated as partners within an organization, project, or collaborative relationship.
-
D.
allowsAffiliationOf
Indicates that one entity grants permission or enables another entity to establish or hold an affiliation with it.
-
E.
associatedWorkKey
Indicates that there is a connection or linkage between one work and another related work, typically identifying the related work by a key or identifier.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.