Triple
T6318196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jayme |
E141666
|
entity |
| Predicate | hasInformalUsage |
P70028
|
FINISHED |
| Object | familiar form of James |
—
|
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: familiar form of James | Statement: [Jayme, hasInformalUsage, familiar form of James]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInformalUsage Context triple: [Jayme, hasInformalUsage, familiar form of James]
-
A.
usedInformallyAlongside
Indicates that something is employed in an informal, non-standard way together with or in addition to something else.
-
B.
hasInformalStatus
Indicates that an entity holds a non-official, casual, or unofficial standing or role in relation to another entity.
-
C.
usedInSpokenForm
Indicates that something (such as a word, name, or expression) is employed in spoken language or oral communication.
-
D.
isLessFormalThan
Indicates that one entity has a lower level of formality or is more casual in style, tone, or usage compared to another entity.
-
E.
usedInFormalContexts
Indicates that something is employed or occurs primarily within formal or official situations, settings, or styles of communication.
- 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_69c008d13b8c8190be47d896eb735605 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c064c38fe48190a71a4e5e1af19b10 |
completed | March 22, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69c060e5efc48190861b8266e5b0cc0c |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623bb29081908bfdfb84a07ece90 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:29 p.m.