Triple
T14480772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Distinction between Common Love and Heavenly Love |
E359095
|
entity |
| Predicate | evaluatesAsNoble |
P114365
|
FINISHED |
| Object | love seeking moral excellence |
—
|
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: love seeking moral excellence | Statement: [Distinction between Common Love and Heavenly Love, evaluatesAsNoble, love seeking moral excellence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: evaluatesAsNoble Context triple: [Distinction between Common Love and Heavenly Love, evaluatesAsNoble, love seeking moral excellence]
-
A.
hasNoble
Indicates that one entity possesses or is associated with a noble title, status, or noble individual.
-
B.
hasNobleStatus
Indicates that an entity possesses a recognized noble rank, title, or aristocratic status.
-
C.
nobleRankAbove
Indicates that one entity holds a higher noble rank or title in a hierarchy than another entity.
-
D.
nobleRankIn
Indicates that an entity holds a specified noble rank within a particular political or territorial jurisdiction.
-
E.
nobleRankType
Indicates the specific category or level of nobility associated with an entity within a hierarchical noble rank system.
- 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_69d827966698819082e140837737501d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de924a576c819098351efabdb779b1 |
completed | April 14, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69de5c487b4c819097803e58dca628a5 |
completed | April 14, 2026, 3:24 p.m. |
| PDg | Predicate description generation | batch_69de5fb4de14819092acdecbd201d672 |
completed | April 14, 2026, 3:39 p.m. |
Created at: April 10, 2026, 1:20 a.m.