Triple
T32485328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Probie |
E830223
|
entity |
| Predicate | appliedToCharacterStatus |
P134515
|
FINISHED |
| Object | less experienced 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: less experienced agent | Statement: [Probie, appliedToCharacterStatus, less experienced agent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedToCharacterStatus Context triple: [Probie, appliedToCharacterStatus, less experienced agent]
-
A.
appliesToCharacter
Indicates that an action, rule, or property is specifically directed toward or relevant for a particular character.
-
B.
refersToCharacterStatus
Indicates that one entity references or denotes the status or condition of a specific character.
-
C.
appliedToStatus
chosen
Indicates that an action, rule, or condition is associated with or affects a particular status or state.
-
D.
marksStatusChangeForCharacter
Indicates a point or event that signifies a change in a character’s status or state within a system or narrative.
-
E.
leadCharacterStatus
Indicates the role or condition of an entity when it serves as the primary or central character in a narrative or context.
- 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_69fecd0a732c819097bdd3eb69b6158c |
completed | May 9, 2026, 5:58 a.m. |
| PD | Predicate disambiguation | batch_69fecc0318d481908b5b20598a76a9fe |
completed | May 9, 2026, 5:54 a.m. |
Created at: May 1, 2026, 12:58 a.m.