Triple
T2230297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Graduate Management Admission Council |
E48747
|
entity |
| Predicate | hasAssessmentType |
P16808
|
FINISHED |
| Object | computer-adaptive 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: computer-adaptive tests | Statement: [Graduate Management Admission Council, hasAssessmentType, computer-adaptive tests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssessmentType Context triple: [Graduate Management Admission Council, hasAssessmentType, computer-adaptive tests]
-
A.
hasTrainingType
Indicates that an entity is associated with or characterized by a specific type or category of training.
-
B.
hasActivityType
Indicates the specific kind or category of activity associated with an entity or event.
-
C.
haveType
chosen
Indicates that an entity belongs to or is classified under a specified type or category.
-
D.
hasApproachType
Indicates the specific method, strategy, or manner in which an action, process, or interaction is carried out or approached.
-
E.
hasAnswerType
Indicates that a question or query is associated with a specific type or category of expected answer.
- 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_69a88aa51b388190949868ec9766e587 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc069e0ac8190bcda8cba9f5c7a5d |
completed | March 7, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69abbdadbb0c8190b3a1ede31b8acbfa |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.