Triple
T10157848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 959 |
E233815
|
entity |
| Predicate | definesClientServerModel |
P92335
|
FINISHED |
| Object | FTP client |
—
|
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: FTP client | Statement: [RFC 959, definesClientServerModel, FTP client]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesClientServerModel Context triple: [RFC 959, definesClientServerModel, FTP client]
-
A.
modelingClient
Indicates that one entity serves as a client that is being modeled or represented by another entity in a modeling context.
-
B.
introducedAsModel
Indicates that one entity is presented or identified to others in the role or capacity of a model.
-
C.
registerModel
Indicates the action of adding or enrolling a model into a system or registry so it becomes recognized and available for use.
-
D.
concurrentModel
Indicates that two or more processes, activities, or states occur or are valid at the same time, potentially interacting or overlapping in execution.
-
E.
intendedClients
Indicates the entities that a product, service, or action is specifically designed or targeted to serve as clients.
- 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_69ca848e80748190b91d1e04d35512c7 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdec5507f08190b47f797bacd5640c |
completed | April 2, 2026, 4:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba795808190acc9124c98c6e40f |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4f8f869c8190a82ad040993e0244 |
completed | April 1, 2026, 5:02 p.m. |
Created at: March 30, 2026, 9:09 p.m.