Triple
T38016605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 9Life |
E948514
|
entity |
| Predicate | importsProgrammingFrom |
P189966
|
FINISHED |
| Object | United States |
—
|
NE NERFINISHED |
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: United States | Statement: [9Life, importsProgrammingFrom, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: importsProgrammingFrom Context triple: [9Life, importsProgrammingFrom, United States]
-
A.
importedWith
Indicates that one entity was brought into a system, context, or location together with or as part of another entity during an import process.
-
B.
extendsProgramsFrom
Indicates that one program is derived, expanded, or built upon the functionality or structure of another program.
-
C.
imported
Indicates that something was brought into a country, system, or context from an external source.
-
D.
primaryImports
Indicates that one entity is the main or predominant source from which another entity imports goods, services, or resources.
-
E.
extendsProgramsOf
Indicates that one program builds upon, enhances, or broadens the scope of another program’s content, features, or capabilities.
- F. None of above. chosen
Provenance (4 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_69f76efc10448190aff5fb566b98f952 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69fc4747b06c8190a3ea5331f02eedad |
completed | May 7, 2026, 8:03 a.m. |
Created at: May 3, 2026, 4:20 p.m.