Triple
T63870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IPv4 |
E1269
|
entity |
| Predicate | headerMaximumSize |
P3276
|
FINISHED |
| Object | 60 bytes |
—
|
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: 60 bytes | Statement: [IPv4, headerMaximumSize, 60 bytes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headerMaximumSize Context triple: [IPv4, headerMaximumSize, 60 bytes]
-
A.
hasMaximumDepth
Indicates that an entity possesses a greatest or limiting depth value beyond which it does not extend.
-
B.
maximumService
Indicates that an entity provides the highest allowable or achievable level of service within a given context or system.
-
C.
packetSize
chosen
Indicates the size or amount of data contained in a packet within a communication or data transfer context.
-
D.
seriesLengthMaximum
Indicates the maximum allowable or observed length (e.g., number of items or installments) in a series.
-
E.
typicalHeight
Indicates the usual or characteristic height associated with an entity, such as a person, object, or species.
- 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_69a24ba4f760819081f6638a3c70538a |
completed | Feb. 28, 2026, 1:57 a.m. |
| NER | Named-entity recognition | batch_69a24fd16c248190a6ee4cd96c388772 |
completed | Feb. 28, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69a24ea3c44081908fa3856969881d1f |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 2:02 a.m.