Triple
T3976271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | In My Business |
E85649
|
entity |
| Predicate | primarySubjectMatter |
P450
|
FINISHED |
| Object | protecting one’s private life |
—
|
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: protecting one’s private life | Statement: [In My Business, primarySubjectMatter, protecting one’s private life]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primarySubjectMatter Context triple: [In My Business, primarySubjectMatter, protecting one’s private life]
-
A.
primaryTopicOf
Indicates that a given subject is the main or central topic described by another resource (such as a document, page, or record).
-
B.
subjectMatter
chosen
Indicates the topic, theme, or content area that something (such as a work, document, or discussion) is about.
-
C.
primaryInterest
Indicates that one entity is the main or most significant focus of attention, concern, or engagement for another entity.
-
D.
primaryArea
Indicates that one entity is the main or most important area, domain, or field associated with another entity.
-
E.
primaryConcept
Indicates that one concept is the main or central idea in relation to another concept or context.
- 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_69aed93908348190a26c8aaf4fab3e86 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaca33e4819091957c7915857a42 |
completed | March 9, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69aef8f252b081909749d40440d372b2 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:33 p.m.