Triple
T5028142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RC2 |
E113227
|
entity |
| Predicate | wasProprietary |
P27024
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [RC2, wasProprietary, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasProprietary Context triple: [RC2, wasProprietary, true]
-
A.
wasProprietaryUntil
Indicates that something was owned or controlled as proprietary (not publicly available or open) up to a specified point in time.
-
B.
hasProprietaryStatus
chosen
Indicates that something is owned, controlled, or protected as proprietary rather than being public or freely available.
-
C.
containsProprietaryComponents
Indicates that one entity includes or is composed of components that are proprietary (owned, controlled, or restricted by a particular party).
-
D.
allowsProprietaryDerivativeWorks
Indicates that one party grants permission for others to create and distribute derivative works that may be kept proprietary rather than shared under the same open terms.
-
E.
ownedProperty
Indicates that one entity possesses legal ownership or control over another entity as property.
- 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_69bd443775e48190a646ffbfc4334723 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd738d852c8190a122354f1e1f5343 |
completed | March 20, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69bd71509e9c8190a60c1d8d04936a12 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:36 p.m.