Triple
T34676821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Satisfaction with Life Scale |
E890513
|
entity |
| Predicate | hasGood |
P179892
|
FINISHED |
| Object | internal consistency |
—
|
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: internal consistency | Statement: [Satisfaction with Life Scale, hasGood, internal consistency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGood Context triple: [Satisfaction with Life Scale, hasGood, internal consistency]
-
A.
hasFair
Indicates that an entity organizes, hosts, or is associated with a fair or similar event.
-
B.
hasQualifying
Indicates that one entity possesses or meets a specific condition, attribute, or criterion that qualifies it in relation to another entity or context.
-
C.
hasPar
Indicates a relationship where one entity has another entity as its parent.
-
D.
hasSam
Indicates that one entity possesses, contains, or is associated with an entity named or identified as Sam.
-
E.
hasCredit
Indicates that an entity possesses or is assigned a credit, such as financial credit, academic credit, or acknowledgment for a contribution.
- 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_69f349dabc008190a18999c26682ed47 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f728a345488190bd7e6751b09ac591 |
completed | May 3, 2026, 10:51 a.m. |
| PD | Predicate disambiguation | batch_69f7283ef2608190a7a85d7e7f5332c0 |
completed | May 3, 2026, 10:49 a.m. |
| PDg | Predicate description generation | batch_69f728a1a0d081909e1b4465e7b88390 |
completed | May 3, 2026, 10:51 a.m. |
Created at: May 1, 2026, 2:05 a.m.