Triple
T27192411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ESFJ |
E683509
|
entity |
| Predicate | hasTertiaryFunction |
P146043
|
FINISHED |
| Object | Extraverted Intuition |
—
|
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: Extraverted Intuition | Statement: [ESFJ, hasTertiaryFunction, Extraverted Intuition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTertiaryFunction Context triple: [ESFJ, hasTertiaryFunction, Extraverted Intuition]
-
A.
hasTertiaryComponent
chosen
Indicates that an entity includes or is associated with a third-level (tertiary) component within a hierarchical structure or system.
-
B.
hasPrimaryFunction
Indicates that one entity serves as the main or principal function or role of another entity.
-
C.
hasSubordinateFunction
Indicates that one function operates under the authority, control, or scope of another function as its subordinate.
-
D.
hasSecondaryUsage
Indicates that an entity is associated with an additional, non-primary function or purpose beyond its main intended use.
-
E.
hasMassOfTertiary
Indicates that a tertiary object or component possesses a specified mass.
- 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_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
Created at: April 27, 2026, 9:32 a.m.