Triple
T23342401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Auburn system |
E591768
|
entity |
| Predicate | viewOnSocialContact |
P125535
|
FINISHED |
| Object | limited supervised association during work |
—
|
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: limited supervised association during work | Statement: [Auburn system, viewOnSocialContact, limited supervised association during work]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewOnSocialContact Context triple: [Auburn system, viewOnSocialContact, limited supervised association during work]
-
A.
socialView
Indicates a relationship where one entity views, accesses, or inspects another entity’s social-related information, profile, or activity.
-
B.
socialProfile
Indicates that an entity has an associated social media or online networking profile.
-
C.
viewOnPerson
chosen
Indicates that one entity holds a particular opinion, perspective, or attitude toward another person.
-
D.
viewOnCommunity
Indicates a perspective, opinion, or stance that an entity holds regarding a particular community.
-
E.
viewOnChosenPeople
Indicates a stance or perspective someone holds regarding a particular group designated as “chosen people.”
- 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_69e25d20e3d08190bcede87673cafb25 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f198334dec819081c432b434eb3ba5 |
completed | April 29, 2026, 5:33 a.m. |
| PD | Predicate disambiguation | batch_69effcfd8d288190937a887fe6023c11 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:18 p.m.