Triple
T28795471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lê dynasty |
E727073
|
entity |
| Predicate | culturalFlourishingIn |
P16953
|
FINISHED |
| Object | literature |
—
|
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: literature | Statement: [Lê dynasty, culturalFlourishingIn, literature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: culturalFlourishingIn Context triple: [Lê dynasty, culturalFlourishingIn, literature]
-
A.
culturalSphere
Indicates that one entity belongs to, is influenced by, or participates in the cultural domain, tradition, or milieu defined by another entity.
-
B.
hasCulturalDevelopment
chosen
Indicates that an entity exhibits, contributes to, or is characterized by a particular level or type of cultural growth, expression, or advancement.
-
C.
culturalFoundationFor
Indicates that one entity provides the cultural basis, background, or supporting context that underlies or enables another entity.
-
D.
culturalMovement
Indicates that an entity is associated with, participates in, or belongs to a particular cultural movement or trend.
-
E.
hasCulturalCommunity
Indicates that an entity is associated with, belongs to, or is part of a specific cultural community.
- 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_69f0319b7c44819085736bcc256185e6 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 28, 2026, 6:25 a.m.