Triple
T27192418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ESFJ |
E683509
|
entity |
| Predicate | prefersFocus |
P31
|
FINISHED |
| Object | outer world of people and activities |
—
|
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: outer world of people and activities | Statement: [ESFJ, prefersFocus, outer world of people and activities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prefersFocus Context triple: [ESFJ, prefersFocus, outer world of people and activities]
-
A.
canonicalFocus
Indicates that one entity is the primary or most representative focus or point of attention in relation to another entity.
-
B.
accessibilityFocus
Indicates that a particular user interface element is currently the primary target of accessibility tools, such as screen readers or keyboard navigation.
-
C.
focusOf
Indicates that one entity is the primary subject, target, or center of attention, activity, or interest for another entity.
-
D.
focusesOn
chosen
Indicates that one entity directs its attention, effort, or primary activity toward another entity or specific subject.
-
E.
focusesBy
Indicates that one entity directs its attention, effort, or emphasis toward another entity or specific aspect of it.
- 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_69eefad140408190b8586fdebcf9af46 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c663be481908f233d25d28713a4 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 9:32 a.m.