Triple
T27755350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UUCP |
E701319
|
entity |
| Predicate | typicalAddressFormat |
P31500
|
FINISHED |
| Object | host1!host2!user |
—
|
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: host1!host2!user | Statement: [UUCP, typicalAddressFormat, host1!host2!user]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAddressFormat Context triple: [UUCP, typicalAddressFormat, host1!host2!user]
-
A.
addressFormat
chosen
Indicates the standardized structure or pattern in which an address’s components are arranged and written.
-
B.
traditionalAddress
Indicates that one entity is the conventional or customary form of address (e.g., title, honorific, or name) used for referring to another entity.
-
C.
standardAddressed
Indicates that something is handled, processed, or treated according to an established standard or set of formal criteria.
-
D.
typicalDestinationAddress
Indicates the address that is most commonly or usually used as the destination for something or someone.
-
E.
addressType
Indicates the specific kind or category of address associated with an entity (e.g., home, work, billing, or shipping).
- 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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_6a0008225cc081909ff1fd0639859dc4 |
completed | May 10, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_6a0007bac5d8819098aff8031d4abe5d |
completed | May 10, 2026, 4:21 a.m. |
Created at: April 27, 2026, 4:23 p.m.