Triple
T29694119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Type I string theory |
E751295
|
entity |
| Predicate | worldsheetHasBoundaries |
P192220
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Type I string theory, worldsheetHasBoundaries, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worldsheetHasBoundaries Context triple: [Type I string theory, worldsheetHasBoundaries, yes]
-
A.
geographicBoundary
Indicates that one entity serves as a limiting border or edge that defines the geographic extent or separation of another entity.
-
B.
showsBoundaries
Indicates that one entity visually or conceptually delineates the limits, edges, or extents of another entity.
-
C.
hasDefinedBoundaries
Indicates that the entity possesses clearly established and recognized limits or borders that distinguish it from its surroundings or from other entities.
-
D.
BritishClaimedBoundary
Indicates that a boundary or territorial line was asserted or claimed by the British as their own.
-
E.
continentBorders
Indicates that one continent shares a land or maritime boundary directly with another continent.
- 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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69fd026757a081909911a59a78652709 |
completed | May 7, 2026, 9:21 p.m. |
Created at: April 28, 2026, 7:19 p.m.