Triple
T30845604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boulevard des Capucines (Monet) |
E785622
|
entity |
| Predicate | movement represented |
P19335
|
FINISHED |
| Object | flow of traffic |
—
|
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: flow of traffic | Statement: [Boulevard des Capucines (Monet), movement represented, flow of traffic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movement represented Context triple: [Boulevard des Capucines (Monet), movement represented, flow of traffic]
-
A.
movementRepresentedBy
chosen
Indicates that a movement or motion of an entity is depicted, encoded, or symbolized by another entity (such as a sign, pattern, or representation).
-
B.
movementFor
Indicates that one entity moves on behalf of, in support of, or as a representative action for another entity.
-
C.
movementIn
Indicates a relationship where an entity moves within, into, or inside a specified area, space, or container.
-
D.
movementFounded
Indicates that an entity established or initiated the creation of a movement.
-
E.
movementDepicted
Indicates that some form of motion or change in position is visually represented or illustrated.
- 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_69f224b850848190a4af4ccf8ddadcdf |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 29, 2026, 8:46 p.m.