Triple
T1129982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High-A |
E23005
|
entity |
| Predicate | usesProfessionalRules |
P6249
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [High-A, usesProfessionalRules, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesProfessionalRules Context triple: [High-A, usesProfessionalRules, yes]
-
A.
usesRulesFrom
chosen
Indicates that one entity applies, follows, or is governed by the rules defined or provided by another entity.
-
B.
playedUnderRulesOf
Indicates that an activity or game was conducted in accordance with a specified set of rules or regulations.
-
C.
isRuleGoverned
Indicates that an entity’s behavior, structure, or operation is determined and constrained by explicit rules or formal regulations.
-
D.
usesLegalCode
Indicates that one entity applies, references, or operates under a particular legal code in its actions or regulations.
-
E.
regulatesProfessionalPracticeIn
Indicates that one entity has the authority or role to control, oversee, or set rules for how a professional activity is conducted within a particular domain or jurisdiction.
- 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_69a493ec75988190b63a11bafaec29b4 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bc4bc21881909dcfe628f59f3e8c |
completed | March 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69a4bb48de2081909a0dce005b1c9df1 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.