Triple
T18027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Internet |
E356
|
entity |
| Predicate | composedOf |
P402
|
FINISHED |
| Object | interconnected computer networks |
—
|
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: interconnected computer networks | Statement: [Internet, composedOf, interconnected computer networks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: composedOf Context triple: [Internet, composedOf, interconnected computer networks]
-
A.
formedByUnionOf
chosen
Indicates that something is created or defined as the union or combination of multiple other things.
-
B.
commissionedBy
Indicates that one entity has been formally requested, authorized, or hired by another entity to create, perform, or carry out something.
-
C.
worksWith
Indicates that two entities collaborate or perform tasks together in a shared work-related context.
-
D.
complements
Indicates that one entity enhances, completes, or improves another by providing qualities or functions that fit well together.
-
E.
coordinatedWith
Indicates that two or more entities have worked together in an organized, cooperative manner toward a shared task, goal, or activity.
- 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_69a23d7ad88c8190bffe8ab091d86642 |
completed | Feb. 28, 2026, 12:57 a.m. |
| NER | Named-entity recognition | batch_69a242494a548190a5776fb6cad4d4af |
completed | Feb. 28, 2026, 1:18 a.m. |
| PD | Predicate disambiguation | batch_69a23fedf0fc8190ad99bd1da297b14d |
completed | Feb. 28, 2026, 1:07 a.m. |
Created at: Feb. 28, 2026, 1:02 a.m.