Triple
T29734315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Type IIA string theory |
E752413
|
entity |
| Predicate | hasDpBranesFor |
P167819
|
FINISHED |
| Object | even p |
—
|
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: even p | Statement: [Type IIA string theory, hasDpBranesFor, even p]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDpBranesFor Context triple: [Type IIA string theory, hasDpBranesFor, even p]
-
A.
hasBridges
Indicates that one entity possesses, contains, or is characterized by one or more bridges connecting locations or components.
-
B.
hasBranches
Indicates that an entity extends into multiple subordinate parts or offshoots, like limbs, divisions, or sections stemming from a main source.
-
C.
hasNumberOfBridges
Indicates the quantitative relationship specifying how many bridges are associated with a given entity.
-
D.
hasDomes
Indicates that one entity possesses or features one or more domes as part of its structure or form.
-
E.
hasCollateralBranch
Indicates that one entity possesses or is associated with a secondary or side branch related to another entity.
- 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_69f0d62a36a88190bf860f00da433ff8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f6733385a081909bea1257ca0b490e |
completed | May 2, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66c59de9881909ebbb7b0ae7ab495 |
completed | May 2, 2026, 9:27 p.m. |
Created at: April 28, 2026, 7:44 p.m.