Triple
T7857607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Logical Awesome LLC |
E182416
|
entity |
| Predicate | platformTypeCreated |
P77929
|
FINISHED |
| Object | web-based version control platform |
—
|
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: web-based version control platform | Statement: [Logical Awesome LLC, platformTypeCreated, web-based version control platform]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: platformTypeCreated Context triple: [Logical Awesome LLC, platformTypeCreated, web-based version control platform]
-
A.
platformName
Indicates the name or identifier of the platform associated with the entity or action.
-
B.
creationPlatform
Indicates the platform, medium, or environment through which something was originally created or produced.
-
C.
platformMate
Indicates that two entities are located on the same platform or share the same platform context at a given time.
-
D.
platformTypeWorkedOn
chosen
Indicates the type of platform on which an entity (typically a person or system) has performed work or carried out activities.
-
E.
announcedPlatform
Indicates that an entity has publicly revealed or introduced a particular platform (such as a system, service, or technology).
- 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_69ca82887fd48190975896bf38c4596b |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb1a76f8648190976b488d0d8658ef |
completed | March 31, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69cae925ca388190ae4a01fa76e957e8 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:52 p.m.