Triple
T13455888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Feudal Japan |
E311229
|
entity |
| Predicate | socialNorms |
P12146
|
FINISHED |
| Object | loyalty to lord |
—
|
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: loyalty to lord | Statement: [Feudal Japan, socialNorms, loyalty to lord]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: socialNorms Context triple: [Feudal Japan, socialNorms, loyalty to lord]
-
A.
levelOfNorm
Indicates the degree or extent to which something conforms to a specified norm, standard, or expected behavior.
-
B.
genderNorms
Indicates socially constructed expectations or rules about how individuals should behave, appear, or identify based on their perceived gender.
-
C.
normativeFor
Indicates that something establishes, prescribes, or encodes the norms, standards, or rules that should govern another thing’s behavior or state.
-
D.
respectedLocalBeliefs
Indicates that one entity acknowledged and behaved in accordance with the customs, traditions, or spiritual practices held by a local community.
-
E.
typicalPractice
chosen
Indicates that an action, behavior, or method is commonly or customarily done in a given context or by a given group.
- 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_69d806a938b8819097ec43a2229fc7f9 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaefc52448190b30d7999f44a9765 |
completed | April 12, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69d9a03ce03481908c61094f0cc0c158 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:41 p.m.