Triple
T25414499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mamba Mentality |
E636791
|
entity |
| Predicate | isAppliedBeyond |
P158277
|
FINISHED |
| Object | personal life goals |
—
|
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: personal life goals | Statement: [Mamba Mentality, isAppliedBeyond, personal life goals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAppliedBeyond Context triple: [Mamba Mentality, isAppliedBeyond, personal life goals]
-
A.
isAppliedBeyond
chosen
Indicates that something (such as a rule, method, or effect) is used or has influence outside its original or primary scope, context, or boundary.
-
B.
appliedAs
Indicates that one entity submitted itself or was put forward for consideration in a particular role, position, or context relative to another entity.
-
C.
appliedFrom
Indicates that an application or request was initiated starting at or originating from a particular source, location, or context.
-
D.
appliedBefore
Indicates that one action, process, or condition was applied earlier in time than another.
-
E.
appliedBy
Indicates that an action, process, or treatment is carried out or executed by a particular agent or entity.
- 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_69e75db4135881909acc287ebcb7a505 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5b010c50881909a6b77af88dd0579 |
completed | May 2, 2026, 8:04 a.m. |
| PD | Predicate disambiguation | batch_69f4806d93dc8190b9dff4c63186faff |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 1:55 p.m.