Triple
T15910317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaplan, Inc. |
E385830
|
entity |
| Predicate | offersPreparationForExam |
P49795
|
FINISHED |
| Object | ACT |
E23985
|
NE 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: ACT | Statement: [Kaplan, Inc., offersPreparationForExam, ACT]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ACT Context triple: [Kaplan, Inc., offersPreparationForExam, ACT]
-
A.
ACT
chosen
ACT is a standardized college admissions test in the United States that assesses high school students' readiness for college-level work.
-
B.
ACT
ACT is the National Rail station code used to identify Acton Town railway station in the United Kingdom’s rail network.
-
C.
ACT
ACT is a renowned nonprofit theater company and acting school based in San Francisco, known for its professional productions and conservatory training programs.
-
D.
ACT
ACT is the standard vehicle registration code used for the Australian Capital Territory in Australia.
-
E.
ACT
ACT is NATO’s strategic command responsible for leading the alliance’s military transformation, innovation, and future capability development.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d86da686e4819097cbf3b1fc2d881d |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1828cd83c8190a3e15cccc8342c1f |
completed | April 17, 2026, 12:45 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffb05750ac81908860143f4ca26cc7 |
completed | May 9, 2026, 10:08 p.m. |
Created at: April 10, 2026, 4:52 a.m.