Triple
T252846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Framers of the United States Constitution |
E5187
|
entity |
| Predicate | metBetween |
P8815
|
FINISHED |
| Object | May 1787 |
—
|
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: May 1787 | Statement: [Framers of the United States Constitution, metBetween, May 1787]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metBetween Context triple: [Framers of the United States Constitution, metBetween, May 1787]
-
A.
locatedBetween
Indicates that one entity is positioned spatially between two other reference entities.
-
B.
dividedBetween
Indicates that something is partitioned or shared among two or more distinct entities or groups.
-
C.
gapBetween
Indicates the spatial or temporal distance or separation that exists between two entities.
-
D.
meets
Indicates that two or more entities come together at the same place and time, typically for interaction or a shared purpose.
-
E.
meetsAs
Indicates that two entities encounter or come together at the same place and time, typically in a planned or recognized interaction.
- F. None of above. chosen
Provenance (4 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_69a257c4bf688190a46ebbf411ab7473 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25d5331b48190b3797fece8e60e20 |
completed | Feb. 28, 2026, 3:13 a.m. |
| PD | Predicate disambiguation | batch_69a25b678d6c81909780e1995c1ca691 |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25c2ca46c81908c61696f31e59a98 |
completed | Feb. 28, 2026, 3:08 a.m. |
Created at: Feb. 28, 2026, 2:54 a.m.