Triple
T2059424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FE Civil |
E45752
|
entity |
| Predicate | examTime |
P35517
|
FINISHED |
| Object | 5 hours and 20 minutes of actual test time |
—
|
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: 5 hours and 20 minutes of actual test time | Statement: [FE Civil, examTime, 5 hours and 20 minutes of actual test time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: examTime Context triple: [FE Civil, examTime, 5 hours and 20 minutes of actual test time]
-
A.
entranceExam
Indicates that an entity is required to pass or participate in an entrance examination as a condition for admission or access to another entity.
-
B.
examProvider
Indicates that one entity is the organization or individual responsible for creating, administering, or supplying an exam to another entity.
-
C.
testTakers
Indicates that certain entities are individuals or groups who participate in taking a specific test or examination.
-
D.
passedExam
Indicates that an entity has successfully met the required criteria to pass a particular exam.
-
E.
examCode
Indicates a relationship where a specific code uniquely identifies or is assigned to an examination or test instance.
- F. None of above. chosen
Provenance (4 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_69a8891a19508190a12ef1e192308dcb |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb9af42988190a4e977154dd10312 |
completed | March 7, 2026, 5:37 a.m. |
| PD | Predicate disambiguation | batch_69abb7ad5a7c8190b92575d6053b3fb7 |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb92f90a881909a1f10b060132a9e |
completed | March 7, 2026, 5:35 a.m. |
Created at: March 4, 2026, 7:40 p.m.