Triple
T8987749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RCAST |
E214710
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | RCAST |
E214710
|
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: RCAST | Statement: [RCAST, abbreviation, RCAST]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RCAST Context triple: [RCAST, abbreviation, RCAST]
-
A.
RCAST
chosen
RCAST is a leading interdisciplinary research institute at the University of Tokyo focused on advanced science and technology.
-
B.
RANC
RANC is the Royal Australian Navy’s principal officer training institution, responsible for educating and preparing naval officers for service.
-
C.
RAC
RAC is the abbreviation for the Royal African Company, a 17th- and 18th-century English trading company heavily involved in the transatlantic slave trade.
-
D.
RAC
RAC is Oracle's clustering technology that allows multiple servers to run a single database instance for high availability and scalability.
-
E.
RCS
RCS (Revision Control System) is an early version control system for managing changes to text files, widely used before more advanced tools like CVS and modern distributed systems.
- 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_69ca839f76bc8190a4b7123cdd682199 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc67f0fed8819098ef3c88f9ef8045 |
completed | April 1, 2026, 12:33 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfd0c155cc819087f1060454da38e5 |
completed | April 3, 2026, 2:37 p.m. |
Created at: March 30, 2026, 7:04 p.m.