Triple
T31902047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brooklyn, Iowa |
E814450
|
entity |
| Predicate | hasPublicSymbol |
P137645
|
FINISHED |
| Object | flag displays throughout the community |
—
|
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: flag displays throughout the community | Statement: [Brooklyn, Iowa, hasPublicSymbol, flag displays throughout the community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublicSymbol Context triple: [Brooklyn, Iowa, hasPublicSymbol, flag displays throughout the community]
-
A.
isPublicSymbol
chosen
Indicates that something functions as a widely recognized sign, emblem, or representation used in public contexts.
-
B.
hasSymbolFor
Indicates that one entity serves as the symbolic representation or sign for another entity.
-
C.
hasPublic
Indicates that an entity is accessible or visible to the general public rather than being private or restricted.
-
D.
hasMainSymbol
Indicates that one entity is designated as the primary or most representative symbol associated with another entity.
-
E.
hasPublicFunction
Indicates that an entity possesses a function or method that is publicly accessible or callable from outside its defining scope.
- 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_69f348f04d7881909537fc9e7cbc670e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: April 30, 2026, 11:59 p.m.