Triple
T29734347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Type IIA string theory |
E752413
|
entity |
| Predicate | includesRRField |
P201493
|
FINISHED |
| Object | 1-form potential C1 |
—
|
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: 1-form potential C1 | Statement: [Type IIA string theory, includesRRField, 1-form potential C1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesRRField Context triple: [Type IIA string theory, includesRRField, 1-form potential C1]
-
A.
includedWith
Indicates that one entity is provided or packaged together as part of another entity.
-
B.
includesRight
Indicates that one entity contains, encompasses, or grants a particular right to another entity.
-
C.
includesResponse
Indicates that one entity contains, incorporates, or encompasses another entity as a response or reply.
-
D.
includesAreaOf
Indicates that one entity encompasses or contains the spatial extent or area covered by another entity.
-
E.
includesFinal
Indicates that one entity contains or encompasses another entity as its concluding or last part.
- 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_69fffbb5d0188190b6d168de8626ff68 |
completed | May 10, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69fffa3bc1208190a277961385a4789f |
completed | May 10, 2026, 3:23 a.m. |
| PDg | Predicate description generation | batch_69fffbb513c881909063ecf12467f4a6 |
completed | May 10, 2026, 3:29 a.m. |
Created at: April 28, 2026, 7:44 p.m.