Triple
T652839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bronze Age |
E11380
|
entity |
| Predicate | hasCulturalDevelopment |
P16953
|
FINISHED |
| Object | early law codes |
—
|
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: early law codes | Statement: [Bronze Age, hasCulturalDevelopment, early law codes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCulturalDevelopment Context triple: [Bronze Age, hasCulturalDevelopment, early law codes]
-
A.
hasCulturalFeature
Indicates that an entity possesses, includes, or is characterized by a particular cultural element, attribute, or landmark.
-
B.
hasCulturalExpression
Indicates that an entity embodies, manifests, or is associated with a particular cultural form, practice, or expression.
-
C.
hasCulturalRole
Indicates that an entity fulfills or is assigned a specific function, position, or significance within a cultural, social, or traditional context.
-
D.
hasCulturalCommunity
Indicates that an entity is associated with, belongs to, or is part of a specific cultural community.
-
E.
hasCulturalSignificance
Indicates that something holds notable meaning, value, or importance within a particular culture or cultural context.
- F. None of above. chosen
Provenance (4 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_69a493266a2881909daf4c40f719dee8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49f4a660c8190b887cb4da01ef7ae |
completed | March 1, 2026, 8:19 p.m. |
| PD | Predicate disambiguation | batch_69a49d1001088190aa7ca3c8f2ad0e32 |
completed | March 1, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69a49dc0e6a08190b81d82a6f2571c41 |
completed | March 1, 2026, 8:12 p.m. |
Created at: March 1, 2026, 7:36 p.m.