Triple
T26987774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Continental (New York) |
E679779
|
entity |
| Predicate | ruleEnforcedBy |
P104153
|
FINISHED |
| Object | The High Table |
—
|
NE NERFINISHED |
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: The High Table | Statement: [The Continental (New York), ruleEnforcedBy, The High Table]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ruleEnforcedBy Context triple: [The Continental (New York), ruleEnforcedBy, The High Table]
-
A.
rulesBy
Indicates that one entity governs, controls, or exercises authoritative power over another entity.
-
B.
alsoEnforcedBy
chosen
Indicates that the same rule, policy, or constraint is enforced by an additional authority, mechanism, or entity beyond the primary one.
-
C.
originallyEnforcedBy
Indicates that a rule, law, policy, or agreement was first implemented and upheld by a particular enforcing authority or agent.
-
D.
isRuleGoverned
Indicates that an entity’s behavior, structure, or operation is determined and constrained by explicit rules or formal regulations.
-
E.
enforcesRule
Indicates that one entity compels or ensures that another entity follows or complies with a specified rule or set of rules.
- 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_69eeeb5138ac8190b3c273ddc659a54f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6215b9bc881909614a84c9f0dc499 |
completed | May 2, 2026, 4:07 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 6:49 a.m.