Triple
T7149915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philadelphia Convention |
E166665
|
entity |
| Predicate | topicDebated |
P57619
|
FINISHED |
| Object | representation in Congress |
—
|
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: representation in Congress | Statement: [Philadelphia Convention, topicDebated, representation in Congress]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topicDebated Context triple: [Philadelphia Convention, topicDebated, representation in Congress]
-
A.
debateTopic
Indicates that one entity serves as the subject or issue being discussed or argued about in a debate involving another entity.
-
B.
fieldOfDebate
Indicates that something is the subject or domain around which a debate or argumentative discussion is centered.
-
C.
debatedWithin
Indicates that something is discussed or argued about within a particular group, context, or domain.
-
D.
mainDebateTopic
chosen
Indicates that a specified subject or issue is the primary focus or central topic of a particular debate or discussion.
-
E.
debatedAs
Indicates that one entity is discussed or argued over in terms of being equivalent to, or serving in the role of, another entity within a debate or comparative argument.
- 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_69c68886779c8190a8e3fbabffe68253 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e7f130e08190bc5ca99f90f9de92 |
completed | March 27, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69c6e1caf4e48190b47bb398a3c1554d |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:46 p.m.