Triple
T13119161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Split |
E311677
|
entity |
| Predicate | featuresNumberOfPersonalities |
P108136
|
FINISHED |
| Object | 23 |
—
|
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: 23 | Statement: [Split, featuresNumberOfPersonalities, 23]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresNumberOfPersonalities Context triple: [Split, featuresNumberOfPersonalities, 23]
-
A.
personalityType
Indicates the specific psychological or behavioral profile that characterizes an entity’s typical patterns of thinking, feeling, and acting.
-
B.
userProfileFeatures
Indicates that certain characteristics, settings, or attributes are associated with and define a user's profile.
-
C.
featuresCharacterWith
Indicates that one entity (such as a work or product) includes or presents a particular character as part of its content.
-
D.
APACharacteristics
Indicates that one entity specifies or describes the attributes, features, or properties of another entity.
-
E.
groupCharacterization
Indicates how a group as a whole is described or characterized in terms of its shared properties, traits, or defining features.
- 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_69d806a9fe888190b081e2d9ea665d6c |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98196e69081909111407ee3d9f08e |
completed | April 10, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69d98041a3548190a05ddd83dbb660fa |
completed | April 10, 2026, 10:57 p.m. |
| PDg | Predicate description generation | batch_69d98134df64819084a5674f9475dcc2 |
completed | April 10, 2026, 11:01 p.m. |
Created at: April 9, 2026, 9:06 p.m.