Triple
T27612372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Time Protocol |
E700358
|
entity |
| Predicate | isStatelessOnServer |
P107863
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Time Protocol, isStatelessOnServer, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isStatelessOnServer Context triple: [Time Protocol, isStatelessOnServer, true]
-
A.
isStatelessPerRequest
chosen
Indicates that the entity does not retain state between individual requests, treating each request as independent and self-contained.
-
B.
stateless
Indicates that an entity does not retain or depend on any internal state between separate interactions or operations.
-
C.
isNonStateRepresentation
Indicates that an entity functions as a representative or representation that is not officially part of, controlled by, or acting on behalf of a sovereign state or its governmental institutions.
-
D.
isStandaloneFriendly
Indicates that an entity can operate or be used effectively on its own without requiring integration or support from other entities.
-
E.
isStateOwned
Indicates that an entity is owned or controlled by a government or state authority.
- 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_69ef6a4f1d9c8190b0705acda054368d |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 27, 2026, 2:11 p.m.