Triple
T7244867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Footprints on the sands of time |
E156442
|
entity |
| Predicate | relatedToLine |
P45024
|
FINISHED |
| Object | Lives of great men all remind us |
—
|
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: Lives of great men all remind us | Statement: [Footprints on the sands of time, relatedToLine, Lives of great men all remind us]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedToLine Context triple: [Footprints on the sands of time, relatedToLine, Lives of great men all remind us]
-
A.
associatedLine
chosen
Indicates that one entity is linked or connected to a particular line (such as a line item, line of text, or line in a structure) with which it is contextually or functionally related.
-
B.
connectedLine
Indicates that two entities are joined by a continuous line or linear connection.
-
C.
relatedTo
Indicates a general, non-specific relationship or association exists between two entities.
-
D.
relatedType
Indicates that one entity is connected to another through a specified type or category of relationship.
-
E.
relatedField
Indicates that one field, topic, or area of study is connected or relevant to another in subject matter or application.
- 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_69c68827b5e481908dc05e145b2c92d4 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ea596fdc8190b2115363f1033441 |
completed | March 27, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69c6e7666ffc81908bf643d8257e6337 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:56 p.m.