Triple
T26765622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eightfold Way |
E674928
|
entity |
| Predicate | providedFoundationFor |
P175211
|
FINISHED |
| Object | quark model |
—
|
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: quark model | Statement: [Eightfold Way, providedFoundationFor, quark model]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providedFoundationFor Context triple: [Eightfold Way, providedFoundationFor, quark model]
-
A.
hasFoundation
Indicates that an entity is supported, established, or based upon a particular foundation or underlying basis.
-
B.
claimsFoundationBy
Indicates that one entity asserts or declares that another entity serves as its basis, origin, or underlying foundation.
-
C.
foundedWithSupportFrom
Indicates that an entity was established or created with assistance, backing, or resources provided by another entity.
-
D.
foundedFor
Indicates that an entity was established or created specifically to serve, support, or benefit another entity or purpose.
-
E.
originalFoundationType
Indicates the type or nature of the initial foundational structure or base on which something was first established or built.
- 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_69eecda85298819097ee1c38a3d772e7 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6cee547108190ad3bc84297d8f516 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
| PDg | Predicate description generation | batch_69f6cee3604c81908a07eade2f39064e |
completed | May 3, 2026, 4:28 a.m. |
Created at: April 27, 2026, 3:59 a.m.