Triple
T268328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York Colonial Assembly |
E5780
|
entity |
| Predicate | metInBuilding |
P1220
|
FINISHED |
| Object | various meeting places in New York City |
—
|
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: various meeting places in New York City | Statement: [New York Colonial Assembly, metInBuilding, various meeting places in New York City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metInBuilding Context triple: [New York Colonial Assembly, metInBuilding, various meeting places in New York City]
-
A.
usesBuilding
Indicates that one entity makes use of, occupies, or operates within a particular building.
-
B.
meets
chosen
Indicates that two or more entities come together at the same place and time, typically for interaction or a shared purpose.
-
C.
isPublicBuilding
Indicates that a building is designated for public use, access, or service rather than being privately owned or restricted.
-
D.
hasEntranceOn
Indicates that one entity’s entrance or access point is located on or faces a specified side, boundary, or feature of another entity.
-
E.
hasRoom
Indicates that an entity possesses, contains, or is associated with a specific room.
- 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_69a2587daeb081909591b9d30f80a271 |
completed | Feb. 28, 2026, 2:52 a.m. |
| NER | Named-entity recognition | batch_69a25dae4a0c8190a66cf6ed3889851c |
completed | Feb. 28, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69a25b70d99c819085d8381a313a2a34 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:56 a.m.