Triple
T6034215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RTCRtpEncodingParameters |
E134377
|
entity |
| Predicate | propertyType_active |
P15519
|
FINISHED |
| Object | boolean |
—
|
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: boolean | Statement: [RTCRtpEncodingParameters, propertyType_active, boolean]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propertyType_active Context triple: [RTCRtpEncodingParameters, propertyType_active, boolean]
-
A.
propertyStatus
Indicates the current condition, state, or classification assigned to a property within a given context (e.g., availability, legal standing, or operational state).
-
B.
architectureProperty
Indicates that a specified architectural characteristic or feature is attributed to, or associated with, an entity.
-
C.
isActive
chosen
Indicates that an entity is currently functioning, engaged, or enabled within a given context or system.
-
D.
propertyTypeOwned
Indicates that one entity owns a specific type or category of property in relation to another entity.
-
E.
builtProperty
Indicates that a constructed structure or building has been created on, or is associated with, a particular property or piece of land.
- 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_69c00875db5c819099dd5bb833ec43c2 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c056b220608190b156be95632cf3b3 |
completed | March 22, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69c049e9a68c81909da0cfe4779ce9b5 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:08 p.m.