Triple
T31359603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La gitanilla |
E799826
|
entity |
| Predicate | workHasMoral |
P102049
|
FINISHED |
| Object | virtue and honor transcend social origin |
—
|
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: virtue and honor transcend social origin | Statement: [La gitanilla, workHasMoral, virtue and honor transcend social origin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workHasMoral Context triple: [La gitanilla, workHasMoral, virtue and honor transcend social origin]
-
A.
moralPositionInWork
Indicates the moral or ethical stance that an entity holds or expresses within a particular work (such as a text, artwork, or performance).
-
B.
moralContent
chosen
Indicates that something contains, expresses, or conveys moral values, judgments, or ethical significance.
-
C.
hasMoralPurpose
Indicates that an entity, action, or decision is guided by or oriented toward ethical values, principles, or morally significant goals.
-
D.
hasMoralFunction
Indicates that an entity serves or fulfills a role related to moral or ethical considerations.
-
E.
hasMoralCode
Indicates that an entity adheres to or is guided by a set of moral principles or ethical rules.
- 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_69f224e5e9bc8190a16339328897c4f8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69f4a00ac8190b7d9fa66781cef1f |
completed | May 3, 2026, 1:05 a.m. |
| PD | Predicate disambiguation | batch_69f69d1d25e88190a7f57d323574da90 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:18 p.m.