Triple
T17022615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princeton architecture |
E412983
|
entity |
| Predicate | sharesMemoryFor |
P125542
|
FINISHED |
| Object | program instructions and data |
—
|
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: program instructions and data | Statement: [Princeton architecture, sharesMemoryFor, program instructions and data]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesMemoryFor Context triple: [Princeton architecture, sharesMemoryFor, program instructions and data]
-
A.
sharesSystemWith
Indicates that two entities operate within or are associated with the same overarching system or environment.
-
B.
sharesAreaWith
Indicates that two entities occupy or overlap the same geographic or spatial area.
-
C.
sharesDamWith
Indicates that two entities are impounded or regulated by the same dam structure.
-
D.
sharesMantleWith
Indicates that two entities occupy or are associated with the same mantle, layer, or mantle-like structure.
-
E.
sharesFieldWith
Indicates that two entities are involved in or associated with the same field, discipline, or area of specialization.
- 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_69d886cc4170819093deddc7b8b4b6a7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d5d1d2e48190bbcba129247c6c2e |
completed | April 18, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_69e35d5be7f48190af9db67a1e23850f |
completed | April 18, 2026, 10:30 a.m. |
| PDg | Predicate description generation | batch_69e3753f93c88190808fec5692f66699 |
completed | April 18, 2026, 12:12 p.m. |
Created at: April 10, 2026, 5:33 a.m.