Triple
T3820423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Praxis tests |
E84357
|
entity |
| Predicate | hasRegistrationRequirement |
P28439
|
FINISHED |
| Object | fee payment |
—
|
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: fee payment | Statement: [Praxis tests, hasRegistrationRequirement, fee payment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegistrationRequirement Context triple: [Praxis tests, hasRegistrationRequirement, fee payment]
-
A.
registrationRequirement
chosen
Indicates that an entity is obligated to formally register with a specified authority, system, or registry under certain conditions.
-
B.
politicalRequirement
Indicates that one entity imposes or must satisfy a political condition, qualification, or constraint in relation to another entity or context.
-
C.
hasRecertificationRequirement
Indicates that an entity is subject to a requirement to periodically renew or update its certification to maintain its valid status.
-
D.
requiresCertification
Indicates that one entity can only be performed, accessed, or considered valid if another entity has an appropriate certification.
-
E.
tradeRequirement
Indicates that a specific condition or set of conditions must be met in order for a trade or exchange between entities to occur.
- 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_69aed931f5908190be2c07af66d4df25 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef188b474819087680db42b04ecdd |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee74a2bc081909b237df8b1e27653 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:17 p.m.