Triple
T8998365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aurora |
E214975
|
entity |
| Predicate | hasSocialNorm |
P22982
|
FINISHED |
| Object | minimal direct human contact |
—
|
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: minimal direct human contact | Statement: [Aurora, hasSocialNorm, minimal direct human contact]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSocialNorm Context triple: [Aurora, hasSocialNorm, minimal direct human contact]
-
A.
levelOfNorm
Indicates the degree or extent to which something conforms to a specified norm, standard, or expected behavior.
-
B.
hasNorm
chosen
Indicates that an entity is associated with, governed by, or characterized through a particular norm, rule, or standard.
-
C.
normativeFor
Indicates that something establishes, prescribes, or encodes the norms, standards, or rules that should govern another thing’s behavior or state.
-
D.
hasSocialObligationsTo
Indicates that one entity bears social duties, expectations, or responsibilities toward another entity.
-
E.
hasSocialPractice
Indicates that one entity engages in, follows, or is characterized by a particular social practice or customary pattern of social behavior.
- 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_69ca83a12d648190b1e4fe11e8a31890 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc68e23734819083a98f4ff0942479 |
completed | April 1, 2026, 12:37 a.m. |
| PD | Predicate disambiguation | batch_69cc5edd6cb48190b4fc6d6ca0418056 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:05 p.m.