Triple
T32100130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FR-08 |
E819822
|
entity |
| Predicate | numericPortion |
P107563
|
FINISHED |
| Object | 08 |
—
|
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: 08 | Statement: [FR-08, numericPortion, 08]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numericPortion Context triple: [FR-08, numericPortion, 08]
-
A.
numericPartRepresents
Indicates that a numeric component of something stands for or encodes a specific value, property, or aspect of that thing.
-
B.
portNumber
Indicates the specific communication port assigned to a network connection, service, or endpoint.
-
C.
registeredPort
Indicates that a specific network port number has been officially assigned and recorded for use by a particular service or protocol.
-
D.
numericSuffix
chosen
Indicates that one entity serves as a numeric ending or trailing number appended to another entity (such as a name, identifier, or string).
-
E.
numericCode
Indicates that an entity is associated with a specific numerical identifier or classification code.
- 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_69f34901106881908ea893ad504a08be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b695bb248190b53b8056dbcf6b55 |
completed | May 3, 2026, 2:44 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:26 a.m.