Triple
T21847087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mac Flecknoe |
E539402
|
entity |
| Predicate | firstLineContains |
P140644
|
FINISHED |
| Object | All human things are subject to decay |
—
|
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: All human things are subject to decay | Statement: [Mac Flecknoe, firstLineContains, All human things are subject to decay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstLineContains Context triple: [Mac Flecknoe, firstLineContains, All human things are subject to decay]
-
A.
firstLineBeginsWith
chosen
Indicates that the first line of a text or document starts with a specified sequence of characters or substring.
-
B.
containsLine
Indicates that one entity includes or encloses a specific line within its spatial or structural extent.
-
C.
isFirstLineOfSystem
Indicates that one entity is the initial or starting line within a defined system or system representation.
-
D.
firstLineOpened
Indicates that the first line of something (e.g., a document, file, or text block) has been opened or accessed.
-
E.
hasFirstLineUpperLevel
Indicates that an entity’s first line is located on or belongs to an upper-level section or tier within a larger structure or hierarchy.
- 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_69e0c476c3c88190a92d08ebb59a128a |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0bd558ed88190a10b8d6752105cd6 |
completed | April 28, 2026, 1:59 p.m. |
| PD | Predicate disambiguation | batch_69e6be8c14748190bdcc44a14d50bea4 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:55 p.m.