Triple
T9898899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Active Server Pages |
E182238
|
entity |
| Predicate | typicalWebServerPort |
P14760
|
FINISHED |
| Object | 80 |
—
|
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: 80 | Statement: [Active Server Pages, typicalWebServerPort, 80]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalWebServerPort Context triple: [Active Server Pages, typicalWebServerPort, 80]
-
A.
typicalPort
chosen
Indicates that a specified port is commonly or normally used for a given service, protocol, or application.
-
B.
typicalServer
Indicates that an entity functions as a standard or representative example of a server within a given context or system.
-
C.
typicalStartPort
Indicates the usual or default port number on which a given service, protocol, or application is expected to start or listen.
-
D.
defaultPort
Indicates that one entity serves as the standard or preconfigured communication port used by another entity unless explicitly overridden.
-
E.
portNumber
Indicates the specific communication port assigned to a network connection, service, or endpoint.
- 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_69ca82876f8081909cf75df0f99bb13f |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb4adc03481909e0f657db01e5bab |
completed | April 2, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69cd1d872d50819096b7ab166a8decf1 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:40 p.m.