Triple
T7920822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maxthon (legacy versions) |
E183938
|
entity |
| Predicate | developedInLanguage |
P12687
|
FINISHED |
| Object | C++ |
—
|
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: C++ | Statement: [Maxthon (legacy versions), developedInLanguage, C++]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developedInLanguage Context triple: [Maxthon (legacy versions), developedInLanguage, C++]
-
A.
developedForLanguage
Indicates that something (such as a tool, system, or resource) was specifically created or adapted to be used with a particular language.
-
B.
developedPrimarilyIn
Indicates that something was mainly created, advanced, or brought into its primary form within a particular context, place, or domain, even if contributions occurred elsewhere.
-
C.
developedWith
chosen
Indicates that something was created, built, or produced using a specified tool, technology, method, or collaborator.
-
D.
originallyDevelopedIn
Indicates that something (such as a product, technology, or idea) was first created, designed, or developed in a particular place or context.
-
E.
developedAs
Indicates that one entity was created, designed, or evolved specifically to function as or replace another entity.
- 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_69ca828efbe48190bd48482650182e79 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a9360f881908ca2433d0623315b |
completed | March 31, 2026, 3:08 a.m. |
| PD | Predicate disambiguation | batch_69cae9316e98819080be7bf1a6ff92f1 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:06 p.m.