Triple
T26966608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EXPTIME |
E679188
|
entity |
| Predicate | relationshipStatusWithNP |
P198916
|
FINISHED |
| Object | NP vs EXPTIME is open |
—
|
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: NP vs EXPTIME is open | Statement: [EXPTIME, relationshipStatusWithNP, NP vs EXPTIME is open]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipStatusWithNP Context triple: [EXPTIME, relationshipStatusWithNP, NP vs EXPTIME is open]
-
A.
relationshipToState
Indicates a relationship or connection that an entity has with a particular state or governmental body.
-
B.
relationshipToNPC
Indicates the type of interpersonal or narrative connection that one entity has with a non-player character (NPC).
-
C.
relationshipManaged
Indicates that one entity oversees, directs, or maintains responsibility for the ongoing management of a relationship involving another entity.
-
D.
inRelationshipWith
Indicates that two entities are mutually involved in a defined personal, romantic, or partnership relationship with each other.
-
E.
associatedPeopleStatus
Indicates the role, condition, or standing of people who are connected or linked to a given entity or event.
- 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_69eeeb4f3a448190b1e94b2d4776c16e |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69ff14d596e88190be5263b7f96a96cd |
completed | May 9, 2026, 11:04 a.m. |
| PD | Predicate disambiguation | batch_69ff13f0208081909369aeb3b77a6b1f |
completed | May 9, 2026, 11:01 a.m. |
| PDg | Predicate description generation | batch_69ff14d4dfc48190bc9fba2384988a98 |
completed | May 9, 2026, 11:04 a.m. |
Created at: April 27, 2026, 6:36 a.m.