Triple
T29694090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Type I string theory |
E751295
|
entity |
| Predicate | hasOpenStrings |
P168174
|
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, hasOpenStrings, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOpenStrings Context triple: [Type I string theory, hasOpenStrings, yes]
-
A.
hasFundamentalStrings
chosen
Indicates that one entity possesses or is characterized by fundamental strings in relation to another entity or theoretical framework.
-
B.
hasStrings
Indicates that an entity possesses or is associated with one or more strings (such as string-like components, text values, or string elements).
-
C.
hasNumberOfSympatheticStrings
Indicates that an entity (typically a musical instrument) is associated with a specific count of sympathetic strings it possesses.
-
D.
hasOpening
Indicates that one entity possesses or features an opening, gap, or entrance that allows access, passage, or exposure.
-
E.
hasOpeningSetting
Indicates that one entity (typically a narrative work) has its initial scene or setting located in the other entity.
- 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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: April 28, 2026, 7:19 p.m.