Triple
T17785352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Untitled 2002 (he promised) |
E444002
|
entity |
| Predicate | usesSpaceAs |
P122947
|
FINISHED |
| Object | site for social interaction |
—
|
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: site for social interaction | Statement: [Untitled 2002 (he promised), usesSpaceAs, site for social interaction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSpaceAs Context triple: [Untitled 2002 (he promised), usesSpaceAs, site for social interaction]
-
A.
usesSpace
chosen
Indicates that one entity occupies, consumes, or makes use of physical or conceptual space associated with another entity.
-
B.
isWrittenWithSpace
Indicates that something is written or represented with spaces separating its components or elements.
-
C.
usesCodeSpace
Indicates that one entity employs or operates within a particular code space or coding environment provided by another entity.
-
D.
baseSpacePreserved
Indicates that a mapping between fiber bundles preserves the underlying base space, leaving the base points unchanged.
-
E.
isWrittenWithoutSpace
Indicates that the referenced elements are written together as a single contiguous string, with no spaces between them.
- 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_69d8b9ef17708190bdf7e2adbf14ddc2 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48792b1c48190836141cfc6656cdd |
completed | April 19, 2026, 7:43 a.m. |
| PD | Predicate disambiguation | batch_69e3d8d8e538819084f1584426b41d5e |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:12 a.m.