Triple
T27192419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ESFJ |
E683509
|
entity |
| Predicate | prefersInformation |
P60489
|
FINISHED |
| Object | concrete facts |
—
|
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: concrete facts | Statement: [ESFJ, prefersInformation, concrete facts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prefersInformation Context triple: [ESFJ, prefersInformation, concrete facts]
-
A.
usesInformationFor
Indicates that one entity applies or exploits information obtained from another entity for a particular purpose or activity.
-
B.
providesInformationIn
Indicates that one entity supplies or conveys information within or through another entity or context.
-
C.
statedPreference
chosen
Indicates that one entity has explicitly expressed or declared a preference for another entity or option.
-
D.
typeOfInformation
Indicates that one entity specifies the category or kind of information that characterizes or describes another entity.
-
E.
usesInformationSources
Indicates that an entity relies on or consults specified information sources to perform actions, make decisions, or obtain knowledge.
- 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_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 9:32 a.m.