Triple
T123243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Educational Testing Service |
E2490
|
entity |
| Predicate | testTypeDeveloped |
P73
|
FINISHED |
| Object | admissions tests |
—
|
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: admissions tests | Statement: [Educational Testing Service, testTypeDeveloped, admissions tests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testTypeDeveloped Context triple: [Educational Testing Service, testTypeDeveloped, admissions tests]
-
A.
hasDevelopmentType
Indicates the type or category of development associated with an entity, such as the nature, form, or stage of its development.
-
B.
developed
chosen
Indicates that one entity created, designed, or brought another entity into a more advanced or complete state through effort or work.
-
C.
developedAt
Indicates the place or location where something was created, built, or developed.
-
D.
codeType
Indicates the classification or category assigned to a particular code within a coding or encoding system.
-
E.
hasTypeOfExperiment
Indicates that an experiment is associated with or classified under a specific type or category of experiment.
- 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_69a251b54ea88190b18281669f59b4c0 |
completed | Feb. 28, 2026, 2:23 a.m. |
| NER | Named-entity recognition | batch_69a2573b4e7481909ee09d2899f8a74b |
completed | Feb. 28, 2026, 2:47 a.m. |
| PD | Predicate disambiguation | batch_69a2564928208190966a619680a0d6e2 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:27 a.m.