Triple
T5538751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Von Steuben Day |
E145233
|
entity |
| Predicate | publiclyMarkedBy |
P34854
|
FINISHED |
| Object | municipal parades |
—
|
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: municipal parades | Statement: [Von Steuben Day, publiclyMarkedBy, municipal parades]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publiclyMarkedBy Context triple: [Von Steuben Day, publiclyMarkedBy, municipal parades]
-
A.
publiclyDisplayed
Indicates that something is shown or made visible in a public context or setting, accessible to people at large.
-
B.
commonlyMarkedBy
chosen
Indicates that one entity is typically characterized, identified, or distinguished by the presence of another entity or feature.
-
C.
reportedMarks
Indicates that an entity has formally communicated or submitted the marks/grades of another entity (such as a student or assessment) to a relevant party or system.
-
D.
publiclyAnnouncedBy
Indicates that an action, decision, or piece of information was formally communicated to the public by a specified agent or entity.
-
E.
usedMark
Indicates that one entity has employed or applied a particular mark, symbol, or indicator in some context or action.
- 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_69c008fa64888190adae56c8f9ea4031 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01fb2fe488190808e02ce5aabb2ad |
completed | March 22, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69c01b0c50e48190a1b03ecd20ca440b |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:35 p.m.