Triple
T32485324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Probie |
E830223
|
entity |
| Predicate | hasRoleContext |
P161
|
FINISHED |
| Object | junior field agent |
—
|
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: junior field agent | Statement: [Probie, hasRoleContext, junior field agent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoleContext Context triple: [Probie, hasRoleContext, junior field agent]
-
A.
hasRole
chosen
Indicates that an entity occupies, performs, or is assigned a specific role or function in relation to another entity or context.
-
B.
hasAdministrativeContext
Indicates that an entity is associated with a particular administrative setting, scope, or jurisdiction that defines how it is governed, managed, or regulated.
-
C.
hasAuthorContext
Indicates that an entity is associated with contextual information about its author, such as background, circumstances, or metadata relevant to authorship.
-
D.
hasProtectionContext
Indicates that an entity is associated with a specific protection-related context that governs how it is safeguarded or controlled.
-
E.
hasRankContext
Indicates that an entity’s rank or ordering is defined, interpreted, or constrained within a specific contextual framework or situation.
- 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_69f34920aa4081908d8fb0277414b911 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd884cb2b48190b6acd473430d9e19 |
completed | May 8, 2026, 6:53 a.m. |
| PD | Predicate disambiguation | batch_69fd8709ca208190a8bab836f0156af5 |
completed | May 8, 2026, 6:47 a.m. |
Created at: May 1, 2026, 12:58 a.m.