Triple
T15291819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ladder of Love |
E365545
|
entity |
| Predicate | progressesTo |
P36477
|
FINISHED |
| Object | appreciation of beauty in all bodies |
—
|
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: appreciation of beauty in all bodies | Statement: [Ladder of Love, progressesTo, appreciation of beauty in all bodies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: progressesTo Context triple: [Ladder of Love, progressesTo, appreciation of beauty in all bodies]
-
A.
progressedBy
Indicates that an activity, process, or state advances or moves forward as a result of the actions or influence of a specified agent or factor.
-
B.
continuesToward
Indicates that an entity maintains its movement or progression in the direction of a specified target or destination.
-
C.
mayAdvanceTo
Indicates that one entity is permitted or eligible to progress, move, or be promoted to another specified state, level, or position.
-
D.
succeedsTo
Indicates that one entity takes over a role, position, or function previously held by another entity, following it in sequence or authority.
-
E.
transitionTo
chosen
Indicates a change in state, condition, or phase from one defined status to another.
- 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_69d85a103d9081908c1ea6c4c73ac8e3 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03680b60c8190a3ea54a9d34c8105 |
completed | April 16, 2026, 1:08 a.m. |
| PD | Predicate disambiguation | batch_69deca90739081909bd1b797cdb8af2b |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:15 a.m.