Triple
T33621146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kyle McAvoy |
E861271
|
entity |
| Predicate | facesDilemmaBetween |
P177440
|
FINISHED |
| Object | career advancement |
—
|
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: career advancement | Statement: [Kyle McAvoy, facesDilemmaBetween, career advancement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: facesDilemmaBetween Context triple: [Kyle McAvoy, facesDilemmaBetween, career advancement]
-
A.
facesConflictWith
Indicates that one entity is in opposition, dispute, or contention with another, involving incompatible goals, interests, or actions.
-
B.
faceDominatesComposition
Indicates that a face is the primary visual element, controlling the viewer’s attention and overall balance of the composition.
-
C.
facedBy
Indicates that one entity is oriented toward and directly opposite another entity, such that it is facing it.
-
D.
mayFace
Indicates that an entity is likely or permitted to encounter, experience, or be subjected to another entity or situation.
-
E.
faceInternalDiversityIn
Indicates that an entity experiences or confronts a range of differing or conflicting elements, perspectives, or characteristics within a specified context or domain.
- 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_69f34980fabc81909819228729a9ca84 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb93224881908fc66fe76115fcdb |
completed | May 3, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f6fb17d5ec81909091e37e1ddbe577 |
completed | May 3, 2026, 7:36 a.m. |
Created at: May 1, 2026, 1:41 a.m.