Triple
T23850936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Unified Theories |
E592165
|
entity |
| Predicate | mayEmbedIn |
P5376
|
FINISHED |
| Object | string theory |
—
|
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: string theory | Statement: [Grand Unified Theories, mayEmbedIn, string theory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayEmbedIn Context triple: [Grand Unified Theories, mayEmbedIn, string theory]
-
A.
canBeEmbeddedIn
chosen
Indicates that one entity can be inserted or integrated within another entity, typically preserving structure or compatibility.
-
B.
mayIncorporate
Indicates that one entity is allowed or able to include, absorb, or integrate another entity as part of itself or its structure.
-
C.
mayHost
Indicates that an entity is permitted or able to serve as the location or organizer for another entity or event.
-
D.
mayPresent
Indicates that one entity is permitted or authorized to present, display, or introduce another entity or item.
-
E.
mayEnter
Indicates that one entity is permitted or authorized to enter or access another entity or location.
- 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_69e25d221d908190b9b502ad31e66a3f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c987c3208190bf3f210d12106927 |
completed | April 29, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f1614612b481908c45d99e588882f9 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:11 p.m.