Triple
T366170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Moveable Feast |
E7963
|
entity |
| Predicate | containsForm |
P12776
|
FINISHED |
| Object | memoiristic sketches |
—
|
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: memoiristic sketches | Statement: [A Moveable Feast, containsForm, memoiristic sketches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsForm Context triple: [A Moveable Feast, containsForm, memoiristic sketches]
-
A.
hasForm
Indicates that one entity possesses, exhibits, or is characterized by a particular shape, structure, or configuration.
-
B.
establishedInCurrentForm
Indicates the point in time when something took on its present structure, organization, or configuration, distinct from any earlier versions or forms.
-
C.
formsWith
Indicates that one entity combines or associates with another to create or constitute a joint structure, group, or configuration.
-
D.
hasFullForm
Indicates that one entity is the complete, expanded, or unabbreviated form of another entity.
-
E.
hasFormulation
Indicates that one entity is expressed, prepared, or configured in a particular form or composition defined by another entity.
- 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_69a2e7e880008190a6ad7e06e5d03007 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebe7d4d0819083daeb7686ae1914 |
completed | Feb. 28, 2026, 1:21 p.m. |
| PD | Predicate disambiguation | batch_69a2e95dbb208190b277fc5352a4ee84 |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2eafc8da88190b4a05182f4384442 |
completed | Feb. 28, 2026, 1:17 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.