Triple
T19702102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pearl Roundabout |
E473121
|
entity |
| Predicate | gatheringFunction |
P65182
|
FINISHED |
| Object | central meeting point for demonstrators |
—
|
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: central meeting point for demonstrators | Statement: [Pearl Roundabout, gatheringFunction, central meeting point for demonstrators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gatheringFunction Context triple: [Pearl Roundabout, gatheringFunction, central meeting point for demonstrators]
-
A.
groupFunction
chosen
Indicates that an entity serves a specific role, purpose, or function within a group or collective context.
-
B.
coordinationFunction
Indicates a relationship where one entity organizes, aligns, or manages the activities or interactions of other entities to ensure they work together effectively.
-
C.
associatedFunction
Indicates that one entity has a related or linked function that is conceptually or operationally connected to it.
-
D.
artifactFunction
Indicates that an artifact is used for, designed for, or serves a particular function or purpose.
-
E.
namingFunction
Indicates a relationship where one entity serves as the name or naming mechanism assigned to another entity.
- 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e642b758348190b0cf58d6b2f13e7f |
completed | April 20, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69e530438c60819082364c7be3eef6f0 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:46 p.m.