Triple
T28028897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prelude |
E708205
|
entity |
| Predicate | thematicallyConnectedTo |
P49998
|
FINISHED |
| Object | Tissues and Issues |
—
|
NE NERFINISHED |
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: Tissues and Issues | Statement: [Prelude, thematicallyConnectedTo, Tissues and Issues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thematicallyConnectedTo Context triple: [Prelude, thematicallyConnectedTo, Tissues and Issues]
-
A.
relatedTheorem
Indicates that one theorem is connected to another through a logical, thematic, or derivational relationship.
-
B.
moreCloselyRelatedTo
Indicates that one entity has a stronger or closer relationship, connection, or similarity to a second entity than to some other reference entity.
-
C.
sharesMathematicalStructureWith
Indicates that two entities exhibit the same or closely analogous underlying mathematical structure, such as isomorphism or structural equivalence.
-
D.
relatedConjecture
Indicates that one conjecture is connected or associated with another conjecture, such as by similarity, dependency, or thematic relation.
-
E.
majorThemeAssociation
chosen
Indicates that one entity is associated with another as a primary or central theme.
- 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_69ef9b6bdd9c8190bb3a574a03774ad1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 8:14 p.m.